bzr log --short ... is not.

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Colin D Bennett wrote:
| On Wed, 11 Jun 2008 12:58:56 -0500
| Russ Brown <pickscrape at gmail.com> wrote:
|> John Arbash Meinel wrote:
|>> Russ Brown wrote:
|>> | John Arbash Meinel wrote:
|>> |> Nicholas Allen wrote:
|>> |> | I wonder if --mainline or --mainline-only would be a better
|>> name for the
|>> |> | --short option. --short implies to me that the message is
|>> shortened or |> | laid out in a short manner. --mainline clearly
|>> indicates that the |> | information you see is only for the
|>> mainline and does not include the |> | merged revisions.
|>> |> |
|>> |> | Nick
|>> |
|>> |
|>> |> True, but it also shortens the rest of the info. The committer
|>> and date |> is put
|>> |> onto one line, it uses a single whitespace line to separate
|>> sections, etc.
|>> |
|>> |> We *could* cap the commit message, I'm not sure how much would
|>> be gained |> by that.
|>> |
|>> |> John
|>> |> =:->
|>> |
|>> | I follow the convention of all commit comments starting with one
|>> brief | line that describes the change. Following that is a more
|>> in-depth | overview. I know that others also follow this practice.
|>> |
|>> | Cutting it at the first linebreak makes a lot of sense in this
|>> case. |
|>>
|>> Hence we have "bzr log --line".
|>>
|>> John
|>> =:->
|> - --line might be what the OP is actually looking for then?
|
| Yes, I got confused. :-(  Sorry to bother you, I was in a hurry when I
| posted the question.  I forgot what --short actually did.
|
|
| On that topic, it might be nice to have an in-between option, e.g., a
| two-line-per revision that uses the first line of the commit message,
| like:
|
|  770: Colin D Bennett 2008-06-10
|  Completed high resolution TSC timer implementation for x86 arch.
|
| Because often the 'log --line' output truncates the commit message to
| such a degree that it is hard to tell what it is and 50% more space
| might help.
|

Well, we do detect the width of your terminal. So if you need 50% more space,
try making your term a bit wider. :)

| I'm not asking anyone to do anything, just musing over possible
| improvements.  Maybe I'll play with this in my spare time.
|
| Colin

The code should be fairly pluggable. You should be able to just register a new
LogFormatter and have it available as "bzr log --format=XXX" (or even just
- --XXX). As an interesting side effect, it will also show up for "bzr missing"
and a few other commands that use that registry.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkhQLnUACgkQJdeBCYSNAAP5yACfRKx1Aa76dArsZ4GQnL34cNA8
60QAoJEKgclxcKkPnCaB4vXiJuUCCUZO
=cpWv
-----END PGP SIGNATURE-----