Re: Project- vs. Package-Level Branching in Git
- From
Jay Soffian <jaysoffian@gmail.com>
- Date
- Jan 28, 2011, 08:30 UTC
- Message-ID
- <AANLkTikLse9+CTwHo6W49=EHj6O4xLSWmNj70RFTpzzb@mail.gmail.com>
- In-Reply-To
- <15B7CA2E-C584-4563-B9E3-D80861CD9565@shaggyfrog.com>
On Thu, Jan 27, 2011 at 6:22 PM, Thomas Hauk <tom@shaggyfrog.com> wrote:
> Git just doesn't seem to scale when it comes to componentized projects.
With git the canonical approach, such that it is, is for each component to be its own repo. You then tie the repos together into a project using submodules:
- http://progit.org/book/ch6-6.html - http://www.kernel.org/pub/software/scm/git/docs/git-submodule.html
However, submodules can be a challenge to work with, and so there have been other attempts at tying multiple repos together such as:
- http://source.android.com/source/git-repo.html - https://github.com/apenwarr/git-subtree
j.