[MERGE] Fix bug #248427 by adding a --change option to log.

John Arbash Meinel john at arbash-meinel.com
Thu Sep 25 17:43:47 BST 2008


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



...

> 
> That's what this patch does.

Not entirely. You map "-c N" => "-r N". When it should really be mapped
to "-r before:N..N".

In 'exclusive' mode, that would give a revision plus all of its merged
revisions. While in exclusive mode, it would make sense for "bzr log -r
N" to *only* show the revision in question, regardless of the formatter.

> 
>     john> Which sounds explicitly like what elmo does not
>     john> want. 
> 
> Including or excluding merged revisions sounds like a log option
> actually handled by the log formatters, not something tied to the
> revision range.

I realize that is how we do it now, but I think that is a bit bogus.
'--long' displays more information for a single revision than '--short'
does regardless of merges. (It shows tags, etc.)

> 
>     john> He wants to only see the log of the specific
>     john> revision. Which is also what Scott seemed to be asking
>     john> for.
> 
> This relates to the '[RFC] How various commands display
> revisions' thread: do we want to give a better control to the
> user and how.
> 
> As of today, if you don't want to see the merged revisions, you
> need to use a format that doesn't show them: --line or --short.
> 
> The patch having been approved, I'll merge it, but IMHO, we
> should continue to discuss the matter, and the thread mentioned
> above sounds like a good place :D
> 
>     Vincent
> 

Sure.

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

iEYEARECAAYFAkjbv8IACgkQJdeBCYSNAANdIACfdBl3ELQHa04h1DDWqopINMTe
9AUAniQcKExEU7BFrs6oMEndWHrRYxEd
=tk6m
-----END PGP SIGNATURE-----



More information about the bazaar mailing list