From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "David E(dot) Wheeler" <david(at)kineticode(dot)com>, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: Managing multiple branches in git |
Date: | 2009-06-02 18:14:51 |
Message-ID: | 4A256C1B.8050209@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> "David E. Wheeler" <david(at)kineticode(dot)com> writes:
>
>> Yeah, with git, rather than cd'ing to another directory, you'd just do
>> `git checkout rel8_3` and work from the same directory.
>>
>
> That's what I'd gathered, and frankly it is not an acceptable answer.
> Sure, the "checkout" operation is remarkably fast, but it does nothing
> for derived files. What would really be involved here (if I wanted to
> be sure of having a non-broken build) is
> make maintainer-clean
> git checkout rel8_3
> configure
> make
> which takes long enough that I'll have plenty of time to consider
> how much I hate git. If there isn't a better way proposed, I'm
> going to flip back to voting against this conversion. I need tools
> that work for me not against me.
>
>
Hmm. I confess that I never switch between CVS branches. Instead I keep
a separate tree for each maintained branch. And that's what the
buildfarm does and will continue doing with git. Maybe that's not as
efficient a way for a developer to work, I don't know.
Of course, your work rate gives you much more weight in this discussion
than me ;-)
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-06-02 18:32:44 | Re: Managing multiple branches in git |
Previous Message | Aidan Van Dyk | 2009-06-02 17:57:50 | Re: Managing multiple branches in git |