[Bf-committers] Google Summer of Code Update
cwant at ualberta.ca
Sun Jun 26 01:06:25 CEST 2005
Hans Lambermont wrote:
> As an option : create just one separate tree, but let all projects work
> on their own branch in there. That'll save you lots of diskspace,
> however it doesn't enforce a strict separation so that mistakes are
> possible (ppl committing on the wrong branch).
Sounds good, but I've never done any branching
like this before, and I don't know how well it
will work with keeping in sync with the official
tree (i.e., the 'tracking third party sources'
way of doing things).
Guess I better do some reading ...
More information about the Bf-committers