[Richard Atterer] > However, if I only want to list the contents of "/dir" inside the > repository with "svn list file:///repo/dir", I run into trouble if > "/dir" no longer exists ***in the most recent revision***. Specifying > an earlier revision using the -r switch does not change this. Here is > a complete example (Output of uninteresting commands not included):
This is correct behavior. The -rNNN flag means "take the target at the HEAD revision, and trace its history back to revision NNN, which may be a different name and location". In your case, of course, this fails because the target does not exist at the HEAD revision. What you want instead is the @ notation, called a "peg revision". This replaces "HEAD" in the semantics described above with a revision of your choice: svn list file:///repo/[EMAIL PROTECTED] "List the path in revision NNN which was called /dir at that time." Note that it can also be combined with -r if you wish: svn list -rNNN file:///repo/[EMAIL PROTECTED] "List the path which was known as /dir in revision MMM, but show what it looked like in revision NNN." > FWIW, "svnlook tree -r1 /tmp/repo /a" works just fine. I'll check with upstream to see if that's intentional. Other than that, can I close this bug? I understand that the behavior is not obvious, but it _is_ intentional. Thanks, Peter
signature.asc
Description: Digital signature
