On 30. mars. 2008, at 00.22, Sam Vilain <sam@xxxxxxxxxx> wrote:
Avery Pennarun wrote:
2. You still check into C, then B, then A, but it doesn't actually
matter if you put B and C on a branch first or not, because 'git
push'
will work properly, because it auto-pushes B and C revisions based on
the fact that A refers to them (ie. implicit branches via the
submodule mechanism).
This push failure thing is regrettable; however it's not clear which
branch name the submodules should get. A given commit might exist on
several branches, which one do you choose to name it?
I solved that by adding a "submodule push" that pushes the detached
head of each submodule to its own ref ("refs/submodule-update/commit-
$sha1", imaginatively). I also made "submodule update" try to fetch
that ref when looking for a sha1.
I ran into trouble trying to avoid pushing every submodule for each
"submodule push", and then more or less decided not to use submodules,
so it's not quite fit for public consumption. I still think it's a
sound idea in principle, so I'll clean it up and send it to the list
if there's any interest.
--
Eyvind Bernhardsen
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
