0.18: Too verbose commit

Jari Aalto jari.aalto at cante.net
Thu Aug 2 12:40:01 BST 2007


Hi,

After upgrading to 0.18, the commit is, ahem, way too verbose. It
would be better if these messages appeared only with -v option.

I'd normally expect clean and simple message:

   $ bzr ci -m "- fixed ..."
   Committed revision 1.
   $

That way I can still scroll the screen upward to see my previous
messages. With the above, I can't see (and use texts) from previous
shell prompts.

Jari

....[hundread simila rmessages]
Collecting changes [Entry 124/131] - Stage: .
added patches-original/sakai/.svn/tmp
Collecting changes [Entry 125/131] - Stage: .
added patches-original/sakai/.svn/text-base/sakai-db-interfa.el.patch.svn-base
Collecting changes [Entry 126/131] - Stage: .
added patches-original/sakai/.svn/text-base/sakai-db-util.el.patch.svn-base
Collecting changes [Entry 127/131] - Stage: .
added patches-original/sakai/.svn/text-base/sakai.patch.svn-base
Collecting changes [Entry 128/131] - Stage: .
added patches-original/sakai/.svn/text-base/sakai.patch.txt.svn-base
Collecting changes [Entry 129/131] - Stage: .
added patches-original/sakai/.svn/tmp/prop-base
Collecting changes [Entry 130/131] - Stage: .
added patches-original/sakai/.svn/tmp/props
Collecting changes [Entry 131/131] - Stage: .
added patches-original/sakai/.svn/tmp/text-base
Saving data locally - Stage: .
Updating the working tree - Stage: .
Committed revision 1.
Running post commit hooks - Stage: .




More information about the bazaar mailing list