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

Re: @REV vs -r REV

From: Matthew Pounsett <matt_at_conundrum.com>
Date: Mon, 20 Apr 2009 10:00:22 -0400

Hash: SHA1

On 20-Apr-2009, at 05:23, Bert Huijben wrote:

>> The command
> svn cat http://server/url/file@123 -r 64
> looks at the url http://server/url/file as it was in revision 123,
> and then
> looks at the history of the specified file to retrieve revision 64
> of that
> file. (That file could be copied between r64 and r123)
> svn cat http://server/url/file -r 64
> looks at the url http://server/url/file in the latest revision
> (HEAD), and
> then looks at this file.. and traces the file back to r64.
> svn cat http://server/url/file@64
> is actually svn cat http://server/url/file@64 -r 64, as the -r command
> defaults to the operational revision specified with the @64 syntax.

The reason why this is important is that http://server/url/file@123
and http://server/url/file@64 have the same path, but MAY be different
files unconnected by history.

For example,

% svn info file | grep URL
URL: http://server/url/file

% svn update
At revision 75.

% svn rm http://server/url/file
Committed revision 76.

% svn update
D file
Updated to revision 76.

% svn copy http://server/url/photo http://server/url/file
Committed revision 77.

% svn update
A file

% svn info file | grep URL
URL: http://server/url/file

Now assume some time passes and we make it to revision 123.
References to http://server/url/file@123 will not have a shared
history with http://server/url/file@64 because that file got deleted
at revision 76, and a new file was created at the same path by copying http://server/url/photo
Version: GnuPG/MacGPG2 v2.0.11 (Darwin)



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-04-20 16:01:31 CEST

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