Hi Tim,
you seem to be confused about Peg revisions, you could read about them here:
http://svnbook.red-bean.com/en/1.5/svn.advanced.pegrevs.html
In short, a peg revions (@2, @HEAD, ...) denotes that the item you're looking
for can be found at the specified path at the specified revision. So
svn list -r2 file:///var/tmp/svn-repo/a...@r4
translates to "show me the list in revision 2 for the directory that's named
"a" in revision 4. Peg revisions can be implied and usually default to "BASE"
which is the working copy revision. A peg revision must be a revision number
and cannot be a date, but as above, you can combine peg revisions and the -r
parameter.
Hope that answers your questions.
felix
On Jan 26, 2010, at 2:26 AM, Tim Landscheidt wrote:
> Hi,
>
> I'm a bit baffled by the following behaviour on a small test
> repository where in r2 the directory a and file a/b exist
> and are deleted in HEAD/r4:
>
> | [...@passepartout ~]$ svn --version
> | svn, version 1.6.6 (r40053)
> | compiled Nov 8 2009, 13:09:20
> | [...]
> | [...@passepartout ~]$ svn list file:///var/tmp/svn-repo
> | [...@passepartout ~]$ svn list -r r2 file:///var/tmp/svn-repo
> | a/
> | [...@passepartout ~]$ svn list -r r2 file:///var/tmp/svn-repo/a
> | svn: File not found: revision 4, path '/a'
> | [...@passepartout ~]$ svn list file:///var/tmp/svn-repo/a...@r2
> | b
> | [...@passepartout ~]$
>
> "svn help list" shows "-r" as a valid option, but apparently
> it is only honoured in a directory that is existent in HEAD
> as well? Is there a way to express the '-r {DATE}' syntax
> with the "@" suffix? "@{2009-01-01}" seems to be ignored:
>
> | [...@passepartout ~]$ svn list 'file:///var/tmp/svn-repo/a...@{2009-01-26}'
> | svn: URL 'file:///var/tmp/svn-repo/a' non-existent in that revision
> | [...@passepartout ~]$
>
> TIA,
> Tim
>
>
--
Felix Gilcher
Bitextender GmbH
Paul-Heyse-Str. 6
D-80336 München
felix.gilc...@bitextender.com
http://www.bitextender.com/
Amtsgericht München, HRB 174280
Geschäftsführer: David Zülke, Florian Clever
