Thread (34 messages) flat view 34 messages, 6 authors, 2016-08-11

Re: [RFC] Submodules in GIT

From: Andreas Ericsson <hidden>
Date: 2016-08-11 20:06:35

Andy Parkins wrote:
On Thursday 2006 November 30 15:20, Sven Verdoolaege wrote:
quoted
You can work on the submodule independently.
It's not independent if any part of it is in the supermodule.
quoted
quoted
some of the development of the submodule is contained in the supermodule
then it's not a submodule anymore.
On the contrary, that's exactly what a submodule is supposed to be.
I don't think so.  I think it's just made some complicated normal repository.
I believe that Andy meant "development history" in his above scentence. 
Naturally, using the code from the submodule while being capable of 
developing the submodule separately from the supermodule is what 
submodules are all about.
quoted
How are you going to checkout the right commit of the lixcb repo if
you didn't store it in the supermodule ?
Well, I know what the commit is /that/ was all that was stored.  So I 
(actually supermodule-git does):

cd $DIRECTORY_ASSOCIATED_WITH_SUBMODULE
git checkout -f $COMMIT_FROM_SUPERMODULE

Obviously, this is grossly simplified.  It also requires that HEAD be allowed 
to be an arbitrary commit rather than a branch, but that's already been 
generally agreed upon as a good thing.
It has? We're not talking supermodule specific things anymore, are we?

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help