[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

@REVISION syntax and svn log (for example)

From: Kalin KOZHUHAROV <kalin_at_thinrope.net>
Date: 2005-08-29 10:16:31 CEST

Hi, all.

I just run into this and checking on the on-line book, didn't shed any
light on this...

Using subversion-1.2.3 on Gentoo here (dev-util/subversion-1.2.3-r1).

When can one use @REV (like URL@HEAD, URL@3) and when not?

Which commands accept it and which not? (so far svn log does NOT)...

I tried to use it with svn log and got this error:

$ svn log https://svn.example.com/repos/prjA/trunk/@489
svn: REPORT request failed on '/repos/prjA/!svn/bc/489/trunk/@489'
svn: '/repos/prjA/!svn/bc/489/trunk/@489' path not found

while this works:

$ svn log https://svn.example.com/repos/prjA/trunk/ -r489
------------------------------------------------------------------------
r489 | Kalin.KOZHUHAROV@examle.com | 2005-08-29 15:57:58 +0900 (Mon, 29
Aug 2005) | 2 lines

get that word file modified.

------------------------------------------------------------------------

** of course, URLs and paths are faked **

This also works:

$ svn diff https://svn.example.com/repos/prjA/trunk/@489
https://svn.example.com/repos/prjA/trunk/@488
Index: doc/test.doc
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/msword

(as well as -r489:488)

Any pointers?
The most relevant point I found so far was:
http://svnbook.red-bean.com/nightly/en/svn.developer.usingapi.html#svn.developer.usingapi.urlpath

Kalin.

-- 
|[ ~~~~~~~~~~~~~~~~~~~~~~ ]|
+-> http://ThinRope.net/ <-+
|[ ______________________ ]|
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 29 10:18:44 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.