> One thing missing from cadmium is anything like the wx ability to store > pending sccs delta comments in the active file.
Indeed. I've mostly gotten used to this, and been OK with it because recommit collects all the comments on the deltas it strips, so I have only had to enter bug info one time. But this is cleaner. > The extension adds a new command, "hg message", which manipulates the > pending message, and interposes on several commands which take commit > messages as arguments to use that pending message as the default/initial > editor buffer content. > > It adds -D and -E options to commands that have -l and -m; "-D" takes > the pending commit message as-is, while -E forces you into the editor > (which could be useful with -l). > > I'm not sure what the appropriate way to distribute this (and what > license to drop into it, yadda yadda), and I haven't hooked it up to > cadmium recommit, but here's a teaser: Choice of license: I'm not sure you have many options as a Sun employee. It's going to either be a viral GPLv2 license by way of Mercurial, or if that doesn't apply, then CDDL. I suspect the former. Cadmium: yes, it should be hooked up to recommit. Which begs the question "should it be a separate extension?" It's useful as such, so "probably," though that means mods to hgsetup, and a flag day for existing hg users to go modify their .hgrc. Unless you can simply require it from Cadmium, but I don't think you can get multiple extensions for the price of one .hgrc entry? And speaking of Cadmium, maybe this should be aliased as pbcom? Pending the results of discussion on Dean's suggestion to rename the cdm commands with a "wx" prefix, does that suggest "wxpbcom" for this, as well? --Mark
