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

Re: Adopting unversioned directory on svn up

From: Olaf van der Spek <ml_at_vdspek.org>
Date: Sun, 4 Dec 2016 11:32:47 +0100

On Sun, Dec 4, 2016 at 1:04 AM, Johan Corveleyn <jcorvel_at_gmail.com> wrote:
> I think the most annoying consequence of accidentally checking out
> over an existing directory, without any conflict detection (if the
> --force behaviour would be the default), would be that you cannot
> easily undo the operation. You haven't lost any unversioned data, but
> you can not easily remove the checkout again and "rollback" to the
> state before the checkout.

Happened yesterday, I checked out into / instead of /etc.. svn behaves
slightly different then rsync I guess.

> Suppose you have files a and b locally. And the checkout
> "incorporates" a and b (say they become unmodified because they are
> the same as the repository version) and adds c, d, e, f, g, ... Oops,
> the checkout was accidental. Now how do I remove it again? I don't
> know which files were there before and which were added by the
> checkout. Now imagine this happening with a complex tree structure
> with 10,000 directories and 100,000 files.

Does svn have a command to delete all versioned items?
If not you still have to 'manually' figure out which directories /
files came from the checkout and which ones existed before.

And this only applies to files.. it doesn't applies to directories
going into a conflict state right?

-- 
Olaf
Received on 2016-12-04 11:33:00 CET

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.