rebase: source is descendant of destination

[Yawar Amin]

On 4/22/10 10:42 AM, schrei5 said:
> Hi,
>
> I am just wondering why I can't rebase a changeset to an ancestor.
> I know this would create a new head but it should be possible shouldn't it?
>   

Intuitively, this seems to me like it should be a no-op.

> 4 o
>    |
> 3 o
>    |
> 2 o
>    |
> 1 o
>   

I'm thinking that because of the way a descendant changeset depends on
its parent, to the rebase command this looks like

o 2 + 3 + 4
|
o 1

So when you run

> rebase -s 4 -d 1
>   

it finds that 4 is part of the whole (2 + 3 + 4) set and rebases that
set onto 1, which is a no-op.


HTH,

Yawar


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 258 bytes
Desc: OpenPGP digital signature
URL: <http://selenic.com/pipermail/mercurial/attachments/20100422/cf136652/attachment.pgp>