hoi :)
On Fri, Dec 01, 2006 at 12:12:34PM +0000, Andy Parkins wrote:
> On Friday 2006 December 01 11:10, Sven Verdoolaege wrote:
>
> > You were proposing to create an extra object containing some random value
> > that is disconnected from the repo.
>
> Right, I think I've finally understood what Martin (and you) are
> proposing. You want every commit in the submodule to be propagated up
> to the supermodule as well. Okay.
>
> I don't think it's right, but at least I understand.
Please note that the submodule commits are not part of the supermodule
commit chain, they are part of the supermodule _tree_.
> It seems wrong because it's making commits in the supermodule that aren't
> commits to do with that project.
Of course they are part of your project, just like all the tree and blob
objects, too.
> In my libxcb example; why should every project use libxcb in have to
> store the entire history of libxcb?
Because you want to be able to use the submodule as a repository of its
own, too. Be able to look at its history if you want to.
Be able to merge with new versions of the submodule.
This is what distiguishes a submodule from a pure file-based import of
another project.
> When examining the supermodule history, I won't care about how libxcb
> got to the state its in, and it's just noise in the supermodule
> history. What if I use 10 submodules, the supermodule history won't
> show you anything useful - it's just unrelated submodule commits.
Again: the submodules are part of your supermodule _tree_, not it's
commit chain. So you won't see the submodule commits when you invoke
git-log in the supermodule.
> It gets worse, this is why I was asking for more detail: this commit
> that you're storing in the supermodule. It's the same commit as is in
> the submodule?
It is _the_ commit from the submodule, yes.
> What would the parent commit of that commit be? It has to be the same
> in both, because the commit-hash forces it to be.
It is the commit of the submodule, so its parents point to the submodule
history.
> > > Is that commit in the submodule or the supermodule?
> >
> > It's in BOTH. That's why it's a *sub*module.
>
> If it's in BOTH then the supermodule is a normal git repository. You aren't
> tracking the submodule, you're just including it en masse.
The submodule is part of the entire project, so yes, it is included.
And the supermodule tracks submodule development by storing references
to the submodule history that was used at that time.
Lets try to paint a little diagram:
belongint to:
/--------- supermodule -------\ /---- submodule -------\
commit -> tree +-> blob
| +-> tree -> ...
| +-----------------> commit -> tree -> ...
v |
commit -> tree +-> ... v
| +-----------------> commit -> ...
| |
| v
| commit -> ...
v |
commit -> tree +-> ... v
+-----------------> commit
Both have their independent history, but they are linked as some
submodule versions are part of the supermodule tree.
--
Martin Waitz
Attachment:
signature.asc
Description: Digital signature