➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients chris.jerdonek, eric.araujo, ezio.melotti, ncoghlan, ned.deily, pitrou, terry.reedy
Date 2013-02-27.11:02:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <578362145.67683000.1361962932481.JavaMail.root@zimbra10-e2.priv.proxad.net>
In-reply-to <1361957114.87.0.0152851470776.issue16930@psf.upfronthosting.co.za>
Content 
> Why must we mention graft at all?  I've never had a need for it.  It
> seems simpler and just as effective to run `hg import` on the
> original patch.

`hg graft` actually works in some cases where `hg import` will fail,
because grafting uses the merge logic (so, for example, it is able to
recognize that some files were renamed between branches).
History
Date User Action Args
2013-02-27 11:02:18pitrousetrecipients: + pitrou, terry.reedy, ncoghlan, ned.deily, ezio.melotti, eric.araujo, chris.jerdonek
2013-02-27 11:02:18pitroulinkissue16930 messages
2013-02-27 11:02:18pitroucreate