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

Re: How to update a single file to HEAD revision?

From: Ryan Schmidt <subversion-2006Q1_at_ryandesign.com>
Date: 2006-01-26 14:00:31 CET

On Jan 26, 2006, at 13:16, Ganssauge, Gottfried wrote:

>>> In CVS I would have done "cvs update -A file".
>>> In Subversion I'm trying to use "svn update -rHEAD" but to no avail.
>>> "svn update -r<numeric head revision>" doesn't work either.
>> "svn update -rHEAD file" does what you want. Since "-rHEAD"
>> is implied, so does "svn update file".
> OK, so much I figured already.
> But what about svn update -r<numeric revision>
> Shouldn't that update the file to the state of the numeric revision?

It does exactly that.

> At least it says it does but when you look at the file it's different.
> [later]
> I SEE!!
> It does contain the contents of revision 9's file - revision 9 in
> directory /branches/BRANCH_1/x!
> This probably should be an FAQ!

Which part should be a FAQ? I think we're still talking about
fundamental Subversion functionality here. If you have a working copy
of the repository path /foo/bar (or /branches/branch_1 or whatever)
at revision 10, and now you issue "svn up" and the repository is
currently at revision 30, then you receive all the changes that were
made in /foo/bar (or /branches/branch_1 or whatever) between
revisions 10 and 30. You don't receive any changes that were made to /
spam/eggs/sausage/and/spam or /trunk or any other path, because as
far as the repository is concerned, that has nothing to do with your
working copy of /foo/bar, regardless of whether one may have at some
point in the past been created by copying the other.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jan 26 14:02:54 2006

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.