On Thu, Aug 27, 2009 at 10:41 AM, Alex Ghitza<[email protected]> wrote: > > On Thu, Aug 27, 2009 at 6:30 PM, John Cremona<[email protected]> wrote: >> One reason why I have (temporarily, I expect) stopped using hg queues >> was that it was pointed out to me that the patches I made from there >> (hg export qtip) did not have a proper commit message. I read all the >> documentation, did what it said -- but still there was no commit >> message in the patch. > > Hi John, > > Here is what I do, although it's probably not the right way to do > things: after hg export qtip, I load the resulting patch file in emacs > and insert the commit message by hand. More precisely, I replace the > first line after the hg "comments", which just says [mq] something, > with a reasonable commit message. If I have time and am not sleep > deprived (so, basically never) this also gives me a chance to have a > last look over the patch and see if I forgot anything -- my emacs > displays diff files in a nice readable way, so it's fairly pleasant.
Are you doing hg qnew -e ? # The -e pops up an editor for me to enter a commit message # The -f retroactively saves my changes as a patch # (the changes visible in hg diff) hg qnew -e -f mypatch.patch More info here: http://wiki.sagemath.org/MercurialQueues -- Carlo Hamalainen http://carlo-hamalainen.net --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
