mercurial-queue

I am developing a web database that is already in use for about a dozen separate installations, most of which I also manage. Each installation has a fair bit of local configuration and customization. Having just switched to mercurial from svn, I would like to take advantage of its distributed nature to keep track of local modifications. I have set up each installed server as its own repo (and configured apache not to serve the .hg directories). My difficulty is that the development tree also contains local configuration, and I want to avoid placing every bit of it in an unversioned config file

After using hg qnew and hg qrefresh to create and update a patch that I want to apply to my repository, but the commit message that I wrote when I did hg qnew was not very good, it did not reference the ticket number from trac, and I would like to say something in it about some of the issues that my commit addresses. How do I do something like hg qrewritemycommitmessage . I have examined the docs on the website and I have come up blank. You just do hg qrefresh -m "new commit message" . In addition to $ hg qrefresh -m "new message" suggested by kuy, you can also use $ hg qrefresh -e to edit the

The qrefresh command in the MQ extension don't make sense to me. I'll explain my assumption: If you don't know on which revision should a certain patch be applied, it have a very little value. You just can't theoretically know what does the rejects mean. And even if there are no rejects on a certain revision, you're not sure the whole revision would compile. Once you qrefresh a certain patch in your patch queue, you're actually losing the parent of the next patch in the queue. So that without your intervention this next patch is/might be useless. In order to fix the next patch, you'd better