On Sat, May 4, 2013 at 8:05 AM, John H Palmieri <jhpalmier...@gmail.com> wrote: > > > On Saturday, May 4, 2013 1:18:55 AM UTC-7, Jean-Pierre Flori wrote: >> >> >> >> On Saturday, May 4, 2013 12:05:29 AM UTC+2, John H Palmieri wrote: >>> >>> >>> >>> On Friday, May 3, 2013 2:26:21 PM UTC-7, Sébastien Labbé wrote: >>>> >>>> > * 8 had problems with the patch itself, like a bad commit message or >>>> > a >>>> > malformed patch file. >>>> >>>> What does "bad commit message" means? That the commit message was >>>> forgotten or ? >>> >>> >>> I often produce patch files where the commit message is something like >>> "[mq]: xyz": I produced the patch using queues in Mercurial, exported it, >>> and then I forgot to edit the patch file to make the commit message >>> informative. >>> >> You don't have to edit the commit message afterwards. >> You can use hg qrefresh -m "#12345: blablabla" beforehand. > > > The point is, I have to remember to modify the commit message at some point. > I don't always remember, and neither do some other people, it would seem, > based on the patches I've seen on trac.
Yeah. I used to have a plugin for that, not sure why I disabled it (maybe because it failed if the ticket number didn't show up). - Robert -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
