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

  ----- Original Message -----
  From: johann.petrak@gmail.com
  To: Donald H Locker
  Cc: users@subversion.tigris.org
  Sent: Sunday, August 20, 2006 4:42 AM
  Subject: Re: Making a file in the working directory not be managed by Subversion any more

  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).

I think what you're looking for is referred to as "obliterate", to eliminate a file and all traces of it in the repository. Adding large files and directories is inevitable in a group project. Somebody's going to import the original project software directory called "project-1.2.3" into trunk, and you'll wind up with "trunk/project-1.2.3" instead of just the files in trunk. That class of mistake happens all the time, and it's currently pretty painful to clean up.
Received on Mon Aug 21 17:48:22 2006