Re: git pull on Linux/ACPI release tree
- From
Martin Langhoff <martin.langhoff@gmail.com>
- Date
- Jan 9, 2006, 23:34 UTC
- Message-ID
- <46a038f90601091534s7f4b36a5he05778f1ed82f34@mail.gmail.com>
- In-Reply-To
- <Pine.LNX.4.64.0601091502200.5588@g5.osdl.org>
On 1/10/06, Linus Torvalds <torvalds@osdl.org> wrote:
> Using many branches in the same tree is > definitely the better approach for _distribution_, but that doesn't > necessarily mean that it's the better one for development.
(...)
> So git certainly supports that kind of behaviour, but nobody I know > actually does it that way
Hrm! We do. http://locke.catalyst.net.nz/gitweb?p=moodle.git;a=heads shows a lot of heads that share 99% of the code. The repo is ~90MB -- and we check each head out with cogito, develop and push. It is a shared team repo, using git+ssh and sticky gid and umask 002.
Works pretty well I have to add. The only odd thing is that the fastest way to actually start working on a new branch is to ssh on to the server and cp moodle.git/refs/heads/{foo,bar} and then cg-clone that bar branch away. Perhaps I should code up an 'cg-branch-add --in-server' patch.
regards,
martin