On 1/18/07, allan juul <allan@muly.dk> wrote:
> now, if someone moves that module to another location we will be unable
> (automatically) to retrieve the original module.
>
> $ svn co http://path/to/some/module -r 12345
>
> returns "path not found"
try: svn co -r12345 http://path/to/some/module@12345
$ svn help co
checkout (co): Check out a working copy from a repository.
usage: checkout URL[@REV]... [PATH]
If specified, REV determines in which revision the URL is first
looked up.
http://svnbook.red-bean.com/en/1.1/ch07s03.html
# [...] It's called the peg revision, and it is a revision
# provided to Subversion for the sole purpose of identifying a
# unique line of history. Because at most one versioned resource
# may occupy a path at any given timeor, more precisely, in any
# one revisionthe combination of a path and a peg revision is all
# that is needed to refer to a specific line of history. Peg
# revisions are specified to the Subversion command-line client
# using at syntax, so called because the syntax involves appending
# an "at sign" (@) and the peg revision to the end of the path
# with which the revision is associated.
#
# But what of the --revision (-r) of which we've spoken so much in
# this book? That revision (or set of revisions) is called the
# operative revision (or operative revision range). Once a
# particular line of history has been identified using a path and
# peg revision, Subversion performs the requested operation using
# the operative revision(s). [...]
HTH
// ben
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jan 18 13:19:24 2007