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

[John Arbash Meinel]

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

James Westby wrote:
> On Wed, 2008-09-24 at 15:48 +0200, Vincent Ladeuil wrote:
>> Aaron said:
>>  > log uses an inclusive set, so log -r 1..2 displays the log
>>  > messages for revisions 1 and 2. diff -r 1..2 displays only the
>>  > changes introduced by 2. diff -c 2 is equivalent to "diff -r
>>  > 1..2".
>>
>> In order to be consistent, from an *UI* POV, log -c 2 should
>> therefore display the logs for revision 2 only.
>>
>> That requires defining a 'change' option *specific* to log.
> 
> Can we make log exclusive so that the inconsistency with diff
> is removed?
> 
> It would break compatibility with old versions, and would mean
> that we would have to decide what to do with "bzr log -rx"
> 
> I don't see why it has to be inclusive, and there have been
> a few requests for some way to make it exclusive. "before:"
> would allow you to make it inclusive much more easily than
> it is to make the current one exclusive as well I believe.
> 
> Thanks,
> 
> James
> 
> 
> 

I've considered doing that. Though in this particular case, it is actually
going to cause the opposite effect for elmo et al.

Specifically, if I was implementing "bzr log -c" (in exclusive mode). I would
show the log of the revision, *and* the log of all merged revisions. Which
sounds explicitly like what elmo does not want. He wants to only see the log
of the specific revision. Which is also what Scott seemed to be asking for.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFI2sfFJdeBCYSNAAMRAklJAKDV+oxKlA+DVRX6Qj4pye3/Cp2lkQCguTkz
OkMe1l2Nd5Mw5ghpmvtY2f4=
=GMPj
-----END PGP SIGNATURE-----