[MERGE] Explain revision/range identifiers

[Daniel Clemente]

Aaron Bentley <aaron at aaronbentley.com> writes:

> John Arbash Meinel wrote:
>> most people think diff & merge consider it open ended (include
>> one end, not the other.)
>
> If we were changeset-oriented, it would be true.  But I don't see any
> value in perpetuating that misperception.  To diff, a range denotes two
> states, and the output compares them.
>

  I think that, however, the example is still correct:

+to be open-ended, that is, they include one end but not the other.  For example:
+"bzr log -r 3647..3649" shows the messages of revisions 3647, 3648 and 3649,
+while "bzr diff -r 3647..3649" includes the changes done in revisions 3647 and
+3648, but not 3649.


  Please correct what is wrong in the patch.

  I think that this misperception (open-ended or not) can be clarified in the documentation.



--
Daniel