Vincent Ladeuil <[EMAIL PROTECTED]> writes: > Try 'bzr merge --pull' if that is what you prefer.
That would help a little bit. > Michael> Note how all of the interesting information about > Michael> the bzr changes has been literally "marginalized" by > Michael> indenting the entire log entry (including authorship > Michael> info) by 4 spaces, while the uninteresting merge > Michael> summary info takes the primary focus by having no > Michael> indentation. What we should care about are the > Michael> changes, not the merge commit by which they happened > Michael> to enter our repo. > > <snip/> > > Try 'bzr log --short' or 'bzr --line' or consider writing your > own customized log formatter. Those options do the exact opposite of what I want. The info about which changes actually occurred is now gone, and only the useless merge info remains. As for writing my own log formatter, no thanks. The log format is not documented in the bzr man page (section for "bzr log") or in bzr log --help. -- | Michael Olson | FSF Associate Member #652 | | http://mwolson.org/ | Hobbies: Lisp, HCoop | | Projects: Emacs, Muse, ERC, EMMS, ErBot, DVC, Planner | `-------------------------------------------------------'
pgpxwpoLnTI6r.pgp
Description: PGP signature
_______________________________________________ Dvc-dev mailing list [email protected] https://mail.gna.org/listinfo/dvc-dev
