From the first follow-up mail:
'Then I noticed that "C-x v v C-c C-c" is enough to commit in CVS, but perhaps not in Bazaar.'
Wow.
'Then I noticed that "C-x v v C-c C-c" is enough to commit in CVS, but perhaps not in Bazaar.'
Wow.
That should be: "C-x v v <Type Commit Message> C-c C-c"
Although it's not quite so daunting once you realise that C-x v is the version-control prefix, and 'v' is commit individual file. C-c C-c is just the command sequence to finish editing the commit message.
Once you leave apart the 'finish editing commit message' command, which is really a seperate task, C-x v v is arguably obtuse as a way of saying commit individual file, but on the other hand, C-x v as a prefix for all vcs related functions is easy enough to remember, and 'v' for commit individual file is easy enough to remember too.
In the microsoft world, 'C-x v v C-c C-c' would be replaced by a 10 page wizard most likely, and be far more irritating.
[Please note, I do not condone the use of empty commit messages, that's a heinous crime IMO]
Edit to add:
In my use of emacs with hg, I believe that that sequence will do exactly the same as it does under cvs, and it's reasonable to believe that the vcs-bazaar backend is no different either, so the complaint in the email is likely invalid.
C-c twice is used in several modes to mean "save and close out". It's also what you hit to send an e-mail you're composing, for example. Holding control and pressing c twice is pretty easy, just like whacking v twice for "next action". (C-c usually prefixes commands specific to the buffer's mode, such as "send the definition under the cursor to Python".)
If you ever forget any of this, you can type "C-x v" and then C-h (Help) and it will list all of the keyboard shortcuts prefixed by C-x v, i.e., all shortcuts related to version control. (I find VC shortcuts go straight to muscle memory, but just in case.)
What NikkiA says above about those five keystrokes being a 10 page wizard in other systems is spot-on.