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

checking our old revision of now moved item

From: allan juul <allan_at_muly.dk>
Date: 2007-01-18 10:46:11 CET


or setup/builds acts very much on specific revisions. for instance we
have a configuration file with entries like:

   http://path/to/some/module = r12345

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"

i expect that error behaves om the HEAD state of the repository. it's
true it doesn't exist in HEAD, but it *does exist* in that particular
revision, because:

   $ svn copy http://path/to/some/module -r12345 http://path/to/my/test
   returns "Committed revision 85306"

so subversion will gladly make a copy of that particular revision.
i'm not sure i understand the rationale of that.

not a major thing, just slightly awkward to retrieve old stuff


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jan 18 10:45:58 2007

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.