bzr log --short ... is not.

[Russ Brown]

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

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?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIUBJghXYlbEtYt2wRAg+2AJkBz0g771BN+RNJ87SlH7BoScVSoACg2Yvh
mMg99gSH6JKHb9GHKCc6rP8=
=fxSZ
-----END PGP SIGNATURE-----