John Cremona wrote: > To Carlo: thanks for updating the wiki on queues, which has grown > since I last looked. I find your solution rather counterintuitive > though: surely ones does "hg -qnew" at the beginning of some work, so > that seems a funny time to write the commit message? But I don't > understand what you mean by the comment "The -f retroactively saves my > changes as a patch" either. Surely you are not editing files *before* > the qnew?
Sometimes, yes. I usually use hg qnew -e -f trac_XXXX-do_something.patch after I realize that my most recent changes should comprise a new patch. For example, the changes may be more than a simple revision to the topmost applied patch, on a different topic, highly experimental, etc. I substitute the appropriate ticket number, if I happen to have it. The first commit message just summarizes what I've done so far and perhaps also what's left to do. http://wiki.sagemath.org/MercurialQueues --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
