Re: Managing multiple branches in git - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: Managing multiple branches in git
Date
Msg-id 20090602235323.GA8123@tamriel.snowman.net
Whole thread Raw
In response to Re: Managing multiple branches in git  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Managing multiple branches in git  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
* Tom Lane (tgl@sss.pgh.pa.us) wrote:
> I can't escape the feeling that we're missing something basic here.
> It's allegedly one of git's great strengths that it allows you to easily
> and quickly switch your attention among multiple development branches.
> Well, so it does, if you haven't got any derived files to rebuild.

I hope this isn't anything particularly special because I feel like I've
been doing it forever, but..

==# cvs -z3 co pgsql
==# mkdir pgsql.build
==# cd pgsql.build
==# ../pgsql/configure --my-args-here
==# make
...

Keeps all the build files and everything in pgsql.build and leaves the
pgsql directory pristine..  I've pretty much always done things this way
so I guess I just assumed it was common.  Maybe it's not what you're
looking for though.

Would that help?
Thanks,
    Stephen

pgsql-hackers by date:

Previous
From: "David E. Wheeler"
Date:
Subject: Re: Managing multiple branches in git
Next
From: Alvaro Herrera
Date:
Subject: Re: Managing multiple branches in git