Thread (36 messages) flat view 36 messages, 8 authors, 2016-06-15

Re: Notes on Using Git with Subprojects

From: Sven Verdoolaege <hidden>
Date: 2016-06-15 22:42:42

On Wed, Sep 27, 2006 at 02:01:11PM +0200, Johannes Schindelin wrote:
On Wed, 27 Sep 2006, Martin Waitz wrote:
quoted
On Wed, Sep 27, 2006 at 11:55:22AM +0200, Johannes Schindelin wrote:
quoted
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help