Track patch across branches?

Pierre-Yves David pierre-yves.david at logilab.fr
Tue Dec 4 12:28:17 UTC 2012


On Tue, Dec 04, 2012 at 04:19:50AM -0800, gideon wrote:
> pierre-yves.david wrote
> > On Tue, Dec 04, 2012 at 12:42:51AM -0800, gideon wrote:
> >> Is it possible to determine which branches a patch has been applied to?
> >> Let's
> >> say I fix a bug in the v3.2 branch, then graft or transplant the fix to
> >> other branches. Other than searching for the commit message, how can I
> >> tell
> >> 6 months later which branches the fix has been applied to?
> > 
> > graft leaves meta information behinds, see the `origin` revset
> 
> Let's say I created the patch on branch a, grafted it to branch b, then from
> b to each of c and d. Now I'm looking at the patch on c, and what to know
> where else it's been. origin will presumably tell me b, and then I can run
> origin again on b to get a, but how would I find d? The recursive query
> (query c to get b, then query b to get a) is also clumsy.

There is a mirror function to travel the other way, check the revset doc. If
you want to save the the recursivity write your own revset in a custom
extension.


-- 
Pierre-Yves David

http://www.logilab.fr/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20121204/03216d8a/attachment.asc>


More information about the Mercurial mailing list