Re: Notes on Using Git with Subprojects
- From
- Sven Verdoolaege <skimo@kotnet.org>
- Date
- Sep 27, 2006, 12:44 UTC
- Message-ID
- <20060927124413.GN1221MdfPADPa@greensroom.kotnet.org>
- In-Reply-To
- <Pine.LNX.4.63.0609271358100.14200@wbgn013.biozentrum.uni-wuerzburg.de>
On Wed, Sep 27, 2006 at 02:01:11PM +0200, Johannes Schindelin wrote:
> On Wed, 27 Sep 2006, Martin Waitz wrote: > > On Wed, Sep 27, 2006 at 11:55:22AM +0200, Johannes Schindelin wrote: > > > Nevertheless, you have to take care of the fact that you need to commit > > > the state of the root project just after committing to any subproject.
So what happens if you pull some changes into a subproject? Are you going to create a commit in the root project for each intermediate commit that you pulled into your subproject? If no, then why should you do so if you happen to do these change in your local repo?
> AFAICT this is not the idea of subprojects-in-git.
As already pointed out by Daniel, there is no such thing as "the idea of subprojects-in-git". There are many ideas of subprojects-in-git.
I, for one, would want to commit the changed state of a subproject to the superproject explicitly.
> If you have to track > the subprojects in the root project manually anyway, you don't need _any_ > additional tool (you _can_ track files in a subdirectory containing a .git > subdirectory).
If I switch to a different branch or bisect in the superproject, then the states of the subprojects should be changed accordingly.
skimo