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

From Aidan Van Dyk
Subject Re: Managing multiple branches in git
Date
Msg-id 20090603003115.GJ23972@yugib.highrise.ca
Whole thread Raw
In response to Re: Managing multiple branches in git  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
* Tom Lane <tgl@sss.pgh.pa.us> [090602 20:18]:
> Yeah, I thought about building out of tree, with a different build tree
> for each branch and VPATH pointing at the common source tree (working
> copy).  That would probably work if it weren't that switching to branch
> B and then back to branch A has to advance the filesystem timestamps on
> every file that's different between the two branches.  So it would
> defeat whatever intelligence "make" might have.  Even if ccache is not
> fooled, that's only a very partial solution.

Yes, the linux kernel relies on the build system (for them its the
kbulid makefile setup) having complete knowledge of all dependencies.
So if you switch branches, "make" knows exactly what files *need* to be
rebuilt, based on complete dependencies (including config) and which
ones don't.

a.


-- 
Aidan Van Dyk                                             Create like a god,
aidan@highrise.ca                                       command like a king,
http://www.highrise.ca/                                   work like a slave.

pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: It's June 1; do you know where your release is?
Next
From: Robert Haas
Date:
Subject: Re: Managing multiple branches in git