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 ezio.melotti
Recipients Todd.Rovito, asvetlov, ezio.melotti, ned.deily, roger.serwy, serhiy.storchaka, terry.reedy
Date 2013-06-08.17:49:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> 'Import' is as easy to use as Graft and as far as I know, the result 
> when successful is the same.

I use import while importing patches from the tracker, but once I committed on 2.x it's easier to just graft instead of importing again (importing often requires you to generate a new patch and possibly you have to commit manually again after the import).

> I know I 'should' learn to use kdiff3 effectively, but it seldom works
> right for me,

That's what learning it is supposed to avoid :)

> and the live repository is the wrong place to learn by failure.

As long as you check the result before pushing there shouldn't be any problems.  If the merge goes wrong you can always rollback and try again (or try a different approach).  You can also use "hg diff -c tip" to see the diff of the last commit.
Date User Action Args
2013-06-08 17:49:54ezio.melottisetrecipients: + ezio.melotti, terry.reedy, ned.deily, roger.serwy, asvetlov, Todd.Rovito, serhiy.storchaka
2013-06-08 17:49:54ezio.melottisetmessageid: <>
2013-06-08 17:49:54ezio.melottilinkissue18152 messages
2013-06-08 17:49:53ezio.melotticreate