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

Re: Copying commited WC

From: Nick Patavalis <npat_at_efault.net>
Date: 2005-01-04 22:54:14 CET

On 2005-01-04, Tom Mornini <tmornini@infomania.com> wrote:
> Say all your revisions in the WC are at revision 1.
> You change 1 file, and commit it. That file in your working copy (and
> in the repo)
> is now at version 2, while all other files in the your working copy
> remain at
> version 1. All other files in the repo are, from the perspective of
> your working
> copy, in an unknown state. About the best you could say is they're
> either at 1
> or 1+, or perhaps moved, renamed, or deleted.
> Subversion is politely telling you that it would like you to issue an
> update
> command to get a consistent revision of all the files you're trying to
> operate
> against.

I understand this, but the problem is that I *can't* issue an "svn
update", at least not unconditionally. The situation is like this (if
it was not made clear by the original posting):

I have a working copy (WC). This WC is, as far as "svn status" can
indicate, fully up to date. I want to copy this WC to the repo like

  cd /path/to/WC
  svn cp . svn://host/repo/proj1/tags/tag1

Will this command succeed, or will it fail? What can I do to guarantee
that it will succeed?

I *cannot* do an "svn up", because this will bring to the WC changes
made in the repository by other users, *after* the checkout of the WC,
and *after* the last commit from it. These changes I *do not* want to

So I have a WC which is perfectly valid, and without local
modifications, as far as the user can tell. The problem is I cannot
copy it! Or to be more precise, I don't know if I can copy it or not
without actually issuing the "svn cp" command.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jan 4 23:00:56 2005

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.