Madan U Sreenivasan <[EMAIL PROTECTED]> wrote:
>> [[[
>> Accept -rX-Y, for all svnmerge commands, where X > Y.
>> Before this patch, empty RevisionSet()s were created when X > Y.
>>
>> * contrib/client-side/svnmerge_test.py
>>     (TestCase_RevisionSet.test_reverse_order_input_string): New
>>      test. Try creating a RevisionSet() with a string range, in
>> descending order.
>>
>> * contrib/client-side/svnmerge.py
>>     (RevisionSet.__init__): Sort the input revision range before
>>      filling in RevisionSet._revs.
>> ]]]


Rationale? "svn merge" accepts the reversed order with a different semantic
(reversed merge). I'm worried about the confusion that can issue. I am +1 on a
patch that errors out when X > Y until there is agreement on how to best handle
this.

Giovanni Bajo

_______________________________________________
Svnmerge mailing list
[email protected]
http://www.orcaware.com/mailman/listinfo/svnmerge

Reply via email to