The recommit command, as you figured out, only supports collapsing into a single changeset.
The -m argument can be left out, in which case Mercurial will invoke $EDITOR on a buffer seeded with the comments from all the changesets it's coalescing. To manage multiple changesets, you'll need to go to a multiple repository scheme. I haven't played with it enough to get a feel for a depth vs breadth arrangement of said repos. This is one reason to not recommit until the very last moment: you can do your bug updates based on diffs from separate changesets. (That, and it's almost always useful to keep development/merge/code review changes separate.) --Mark On Mon, 11 Aug 2008, Dan Anderson WFH wrote: > Date: Mon, 11 Aug 2008 23:46:17 -0700 > From: Dan Anderson WFH <Dan.Anderson at sun.com> > To: scm-migration-dev at opensolaris.org > Subject: [scm-migration-dev] Mercurial/hg equivalent for wx redelget > > Dan Anderson wrote: >> What's the Mercurial/hg equivalent for wx redelget? It is supposed to be >> hg recommit, but that doesn't work (below). I typed webrev after hg and it >> showed no changes to the delta descriptions. >> >> I think I can use hg recommit -m "123456 some comment", according to a few >> presentations and cheatsheets, but this webrev has two separate bug >> numbers, one for some files, another CR for other files. >> >> - Dan >> >> $ hg recommit >> remote: Not trusting file /export/onnv-clone/.hg/hgrc from untrusted user >> onhg, group gk >> Do you want to backup files first? [Y/n]: n >> saving bundle to >> /builds/da73024/nv96_bswap_hg/.hg/strip-backup/2b99e508f5c1-temp >> $ >> > > >
