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 chris.jerdonek, eric.araujo, ezio.melotti, ncoghlan, ned.deily, pitrou, terry.reedy
Date 2013-02-28.11:42:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1362051777.54.0.352986557213.issue16930@psf.upfronthosting.co.za>
In-reply-to
Content
> (I will check to see if commit is really 'alwats' or if there is an 
> option to not commit, as with import and merge.)

There isn't AFAIK, but two "tricks" I use are:
 1) "hg diff -c tip" to check the diff of what I just grafted;
 2) "hg rollback" to rollback the commit in case something is wrong;

I'll see if/where they should be added.

> New people should be downloading the latest version of hg.

That works on Windows, but on Unix most people just use the version shipped with their distribution.  "hg graft" is not so bleeding-edge anymore though -- I had it for a while using the default "hg".

> As for case conflicts, how about adding a phrase to produce
> "On older versions of Mercurial where hg graft is not available, or 
> when graft has problems with case conflicts, you can use:"

This (or the wording I suggested in msg183024 if it's accurate) would be ok with me.  Terry, have you tried using "hg graft" yet?  Are there conflicts on Windows?  I'm not sure how common these conflicts are -- I've never seen them myself.

> (note /version/versions/, so a patch is needed anyway ;-).

Yep, I spotted that but was waiting for this issue :)
History
Date User Action Args
2013-02-28 11:42:57ezio.melottisetrecipients: + ezio.melotti, terry.reedy, ncoghlan, pitrou, ned.deily, eric.araujo, chris.jerdonek
2013-02-28 11:42:57ezio.melottisetmessageid: <1362051777.54.0.352986557213.issue16930@psf.upfronthosting.co.za>
2013-02-28 11:42:57ezio.melottilinkissue16930 messages
2013-02-28 11:42:57ezio.melotticreate