subrepo grand plan
Martin Geisler
mg at aragost.com
Thu Oct 20 08:13:25 CDT 2011
"Dominik Psenner" <dpsenner at gmail.com> writes:
> d) make commit subrepo aware
>
> This may sound silly, but as far as I understood subrepositories, a parent
> repository tracks subsets of its subrepository changeset hashes. Shouldn't
> commit to a parent repo then behave like this?
>
> Assuming to have following repositories:
>
> P := parent repo
> A := subrepo A
> B := subrepo B
>
> A commit to the parent repository P executes:
>
> hg commit A # commit file changes
> hg commit B # commit file changes
> cat tip(A) > .hgsubstate
> cat tip(B) >> .hgsubstate
> hg commit P # commit new head with valid hash subset and file changes
That is how subrepositories work today :)
--
Martin Geisler
aragost Trifork
Professional Mercurial support
http://mercurial.aragost.com/kick-start/
More information about the Mercurial-devel
mailing list