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

Re: Branching with missing revisions

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-08-11 19:29:29 CEST

On Wed, 2004-08-11 at 12:23, Kevin Ballard wrote:

> Thanks for the clarification. I'll make sure to always do an svn update
> before trying to create a new branch, even if my WC is up-to-date (and
> by up-to-date I mean all files are at at least their last committed
> revision)

Sorry, I didn't mean to sound like I was yelling before. :-)

It's a common misconception: I don't think everyone realizes that you
have a mixed-revision working copy after *every* commit. Only 'svn up'
will bring your working copy to a single working revision.

The other thing to clarify here is that 'svn cp wc URL' will build a
transaction-tree on the server that is an *exact* reflection of the
mixed revisions in your working copy. So before you run such a command,
run 'svn status -v wc' to see exactly what you're copying to the server.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 11 19:30:54 2004

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.