On Wed, Nov 26, 2008 at 2:51 PM, Branko Èibej <brane_at_xbc.nu> wrote:
> Mark Phippard wrote:
>> On Wed, Nov 26, 2008 at 2:31 PM, Branko Èibej <brane_at_xbc.nu> wrote:
>>
>>> (The usual way to get both URL and REV are to do an svn log -v, find the
>>> set of commits you're looking for, and copy rev and path from there,
>>> never caring about later deletions or renames or whatnot.)
>>>
>>
>> Sorry, but I am still in disagreement. Your example just further
>> solidifies that. Let's use your example. I am naturally working in
>> HEAD and I run svn log -v to look at history. I see some old
>> interesting revision that I want to see more details about. You now
>> want me to also notice that somewhere in the history of the item the
>> name of the item has changed and use that new name when I use
>> subsequent commands. I'd typically assume the filename had not
>> changed and would get a failure.
>>
>
> Huh? You've turned my explanation inside out. I said you get the *old*
> path and rev from the log, and do
>
> svn co -r rev URLBASE/path
I am not specifically trying to turn your examples inside out.
Really. I think this is just an example of that there is not a single
"expectation".
Suppose I do this:
svn log http://svn.collab.net/repos/svn/trunk/subversion/libsvn_ra_neon/session.c
I look through the log and notice r22440 and want to look at it.
svn cat -r22440
http://svn.collab.net/repos/svn/trunk/subversion/libsvn_ra_neon/session.c
This works.
But you want me to notice that during the history of this file it was
renamed from libsvn_ra_dav. So if we made your change, I would have
to actually enter this command:
svn cat -r22440
http://svn.collab.net/repos/svn/trunk/subversion/libsvn_dav/session.c
or this:
svn cat -r22440
http://svn.collab.net/repos/svn/trunk/subversion/libsvn_ra_neon/session.c@HEAD
So I am just saying that I think the current syntax can also make
sense and that it is better for all commands to be consistent.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
Received on 2008-11-26 21:03:09 CET