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

RE: New vendor drops on vendor branch - but how?

From: Gavin Lambert <gavinl_at_compacsort.com>
Date: 2006-08-11 09:39:42 CEST

Quoth Erik Forsberg <mailto:forsberg@cendio.se>:
> I'm experimenting with vendor branches and subversion, trying
> to understand the documentation. I'm a bit confused on the
> procedure when it comes to doing new vendor drops.
> In order to get the desired behaviour, I'd need to clean the
> working copy of all files and directories. But as far as I
> can see, there's no good way to do that without confusing
> svn, or is there? If I do a 'rm -r' in my working-copy, svn
> will have no idea about what files were and weren't available
> in subdirectories, and it will also complain about files
> being missing if I try to tell it to move a file from one location to
> another.
> I know about the svn_load_dirs.pl script, but I'd still like
> to know how to do a vendor drop manually.

Yep, it's definitely a bit confusing in that spot.

I haven't tried this myself (so try it without the 'rm' first to make
sure it gives the right results!), but this ought to remove all files
except for the .svn folders, starting from the current directory:

  find . | grep -v .svn | xargs rm -f

(if you've got files with '.svn' in them for some weird reason, you can
use '/.svn' to cut down the results a bit.)

And note that this will find *all* files, not just version-controlled
ones. So make sure you're doing it in the right place, and you don't
have any unversioned files you care about!

After untarring the vendor drop, you'd have to manually enter any
copies/moves/renames afterwards, though, which'd be a bit painful.
svn_load_dirs.pl is a bit less painful in this regard :)

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 11 09:41:51 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.