hoi :)

On Thu, Nov 30, 2006 at 03:30:49PM +0000, Andy Parkins wrote:
quoted text
> Well, I know what the commit is /that/ was all that was stored.  So I=20
> (actually supermodule-git does):
>=20
> cd $DIRECTORY_ASSOCIATED_WITH_SUBMODULE
> git checkout -f $COMMIT_FROM_SUPERMODULE
>=20
> Obviously, this is grossly simplified.  It also requires that HEAD be all=
owed=20
quoted text
> to be an arbitrary commit rather than a branch, but that's already been=
=20
quoted text
> generally agreed upon as a good thing.

It's not that easy.

You also have to make sure that all your submodule commits that _ever_
have been part of your submodule have be stay in your repository
forever.
Consider that your submodule switches to an other branch and some
old commits are not referenced by the current version any more.
These old commits still have to survive a git-prune, if they have been
part of some old supermodule version.
So you really have to connect both object databases and it's not enough
to just store the commit sha1 without actually parsing it by the GIT
core.

--=20
Martin Waitz