[PATCH 4 of 5 RFC] revset: add a predicate for finding rebased changesets

[Matt Mackall]

On Wed, 2012-05-16 at 13:50 +0200, Pierre-Yves David wrote:
> On Tue, May 15, 2012 at 06:56:40PM +0200, Sune Foldager wrote:
> > 
> > > Matt Harbison <matt_harbison at yahoo.com> writes:
> > > 
> > >> # HG changeset patch
> > >> # User Matt Harbison <matt_harbison at yahoo.com>
> > >> # Date 1336884852 14400
> > >> # Node ID 5de639cd52e36c27b4c8bbbaa5fdb44803efee72
> > >> # Parent  2612b6d41579adce0df8f6b744f2879868125b5b
> > >> revset: add a predicate for finding rebased changesets
> > >> 
> > >> This selects changesets added because of rebases. If a revision is
> > >> specified, the set will be empty if that revision is not the source of
> > >> a rebase, or it will contain a destination changeset for each time the
> > >> specified revision was rebased. This can be useful for figuring out
> > >> where a particular changeset has been propagated.
> > 
> > Rebased changeset originals no longer exist, though, as opposed to grafted and locally transplanted ones, so what would you use it for?
> 
> Various extras key are used:
> 
>     graft:'source',
>     rebase: 'rebase_source',
>     transplant: 'rebase_source',
> 
> A first step seems to unify all this to the common "source" extra.[1]
>
> [1] keep the old one for BC purpose.

That would be nice, but it's orthogonal to this feature. Any revset
predicate has to support ALL of the historical names to be useful.

-- 
Mathematics is the supreme nostalgia of our time.