[issue2314] hg push -r doesn't work as expected with subrepos
Colin Caughie
bugs at mercurial.selenic.com
Mon Aug 2 15:38:07 UTC 2010
New submission from Colin Caughie <c.caughie at indigovision.com>:
I had something like this as unpushed changes in my top level repo and subrepo:
toprepo: t1 --- t2 --- t3 --- t4
| |
| +------+
| |
subrepo: s1 --- s2
In other words, at t3 the top repo moved from subrepo version s1 to version s2.
Once I got t1, t2 and s1 code reviewed by a colleague, I wanted to push
these changesets so I did
> hg push -r t2
To my surprise it pushed _all_ of the outgoing changes in subrepo instead of
just the one that t2 depended on, i.e. s1. This wasn't great because s2 had
not yet been code reviewed.
It would be better if it could push only the revisions from subrepos that
are required by the revisions being pushed from the main repo.
----------
messages: 13276
nosy: ccaughie
priority: bug
status: unread
title: hg push -r doesn't work as expected with subrepos
____________________________________________________
Mercurial issue tracker <bugs at mercurial.selenic.com>
<http://mercurial.selenic.com/bts/issue2314>
____________________________________________________
More information about the Mercurial-devel
mailing list