Home/ Questions/Q 8081661
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-05T16:48:36+00:00

I’m using the graft command to pull 4 changesets from a BranchA into BranchB.

  • 0

I’m using the graft command to pull 4 changesets from a BranchA into BranchB. When I do, some are grafted and some are not: 

PS D:\Dev\ProjectAlpha> hg graft 5f403abb2b24
skipping ancestor revision 15911
PS D:\Dev\ProjectAlpha> hg graft 535ff712c5a3
grafting revision 15925
PS D:\Dev\ProjectAlpha> hg graft cf42b7113e02
grafting revision 15931
PS D:\Dev\ProjectAlpha> hg graft 6920922ee602
skipping ancestor revision 15910

I can’t find anything documented that explains this. I can find the source, but maybe it’d be helpful to someone else if someone could come along and explain this.

Is there an order of operations with graft that I need to keep in mind? Am I doing it wrong?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    From hg help glossary:

    Ancestor
    Any changeset that can be reached by an unbroken chain of parent
    changesets from a given changeset. More precisely, the ancestors of a
    changeset can be defined by two properties: a parent of a changeset is
    an ancestor, and a parent of an ancestor is an ancestor. See also:
    'Descendant'.

    so graft is refusing to make those revisions descendants of your current changeset because they’re already ancestors of your current changeset, and having your ancestors be your descendants was shown to not work in the Back to the Future movies. 😉

    • 0