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

RE: Making a file in the working directory not be managed by Subversion any more

From: Gavin Lambert <gavinl_at_compacsort.com>
Date: 2006-08-22 05:23:34 CEST

Quoth johann.petrak@gmail.com <mailto:johann.petrak@gmail.com>:
> I think an "unversion" command should be a standard part of
> subversion: it can easily
> happen that one puts unwanted files or even directories in the
> repository by accident
> when a big project is initially added.
> It would probably be best to have a command that by default does what
> the workaround
> of copy/svn delete/copyback does, with a --force option that in
> addition removes the complete history of the file from the repository
> (this would be good to have if by accident very large files or
> directories got added).

It's a bit late once it's already in the repository, but to avoid these
sorts of things I simply never use 'svn import' -- instead I use 'svn
mkdir' to create an empty folder, then checkout that folder into my
existing source tree. (SVN won't barf as long as the folder in the repo
is empty, or at least that there aren't any clashing files.) Then I can
specifically 'svn add' whatever files I need, which (since I usually use
TSVN) is as simple as clicking a checkbox at commit time.

Even with the command-line client, you should be able to 'svn add .' or
'svn add *' to add everything (equivalent to an import) and then 'svn
revert' those files that you *don't* want added. Easy, and you get to
verify that you've selected the right set of files before finally

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 22 05:24:53 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.