>> I believe that users expect
>>
>> svn log -rREV1:REV2 path_at_PEG
>>
>> to mean "report everything that happened to path_at_REV between
>> revision REV1 and REV2, inclusive", with both creation and deletion
>> being events for potential inclusion in the report. It's unfriendly
>> for "path_at_PEG does not exist in revision REV1" or "path_at_PEG does not
>> exist in revision REV2" to be fatal errors that prevent the display
>> of information for revisions where path_at_PEG does exist.
>
>> I am not the original poster, but I would ask for this to be changed
>> so that it uses the revision in which path_at_PEG was deleted as an
>> upper limit, and the revision in which path_at_PEG was created as a
>> lower limit, no matter what -r says.
>>
>> I'd also like deletion events to appear explicitly in the log, but
>> that's a separate issue. If ^/dir/subdir/file exists in revision 5,
>> but ^/dir is deleted in revision 6, then I'd like "svn log -v -q -r6
>> ^/dir/subdir/file_at_5" to print
>>
>> r6 | author | timestamp
>> Changed paths:
>> D /dir
>>
>> instead of
>>
>> svn: File not found: revision 6, path '/dir/subdir/file'
>
> Makes sense to me. Is there an existing issue filed for this or
> should we file a new one?
as far as i know there is not yet such an issue in the tracker.
It would be great if you could file one.
Can you post the issue number so that i can put it on my watch list?
I would appreciate the feature since it would also be very useful for tools like WebSVN.
How realistic would it be to get it implemented in the near future?
While having good programming skill i have never compiled subversion myself. But if any help is needed e.g. for testing i would be happy to support.
Thank you,
Dirk
Received on 2011-03-08 11:12:01 CET