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

Re: best practice: current version, wc not updated

From: Erik Huelsmann <ehuels_at_gmail.com>
Date: Mon, 30 Jun 2008 16:55:18 +0200

On 6/30/08, fkater_at_googlemail.com <fkater_at_googlemail.com> wrote:
> Hi,
> I've got some hundrets of subfolders. All files of my wc are
> checked in -- but not all folders are updated (new versions
> on the server are most probable).
> In this situation, what is the best way to find out the
> current version(s) of the files in my wc?
> I simply want to write down the (minimal) set of version
> numbers to document and possibly later restore the exact
> current state of my wc.
> This is what I do:
> * I do 'svn info' in the root dir to get the "last changed"
> revision.
> * I do 'svn status -u' in the root dir to see for which
> files in my wc there are newer versions
> * I do 'svn status -v path/to/each/outdated/file' to get
> the current version of it in my wc.
> Is there a better way?

svn cp . URL/to/my/private/branch

which will allow you to restore your working copy in exactly the way
it was when you saved it.



To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-06-30 16:55:53 CEST

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.