Hi John,

On Thu, Aug 27, 2009 at 6:30 PM, John Cremona<[email protected]> wrote:

<SNIP>

> 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.

The person who pointed that out to you is me :-)


>  I read all the
> documentation, did what it said -- but still there was no commit
> message in the patch.  I'm sure someone will now tell me what is the
> right way to do that (but please don't just point me to the
> documentation this time, as what I fould there sis not work for me!)

In addition to Alex's suggestion, here's another tip to ensure you
have a proper, sensible commit message. After making the necessary
changes, you can refresh your patch with

hg qrefresh -e

where the optional argument "-e" tells Mercurial to open an editor for
you to write your commit message. After you have entered your commit
message in the editor, quit the editor and the commit message is saved
with the refreshed patch.

-- 
Regards
Minh Van Nguyen

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to