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).
On 3/17/06, Donald H Locker <donald.locker@ptmelec.com> wrote:
>
> [apologies to Steve; I first sent this only to him, not the list.]
>
> I tried this, but when I did an svn update, the file was deleted in my
> working directory. (I think this is reasonable behaviour, but it wasn't
> what I really wanted.)
>
> Suggestions?
> (Right now I'm working on a dump/dumpfilter/load script to "unversion"
> all the files that I added at the "beginning of time" that are not
> really source files.)
>
> Donald.
> (is top-posting deprecated on this list?)
>
> Steve Williams wrote:
> > johann.petrak@gmail.com wrote:
> >
> >> What is the best way to make a file that has been managed by
> >> Subversion not be managed any more?
> >> For instance, if a file got accidently added to the repository, how to
> >> remove it from there without removing
> >> it from the working directory? Is there a way to "officially" drop it?
> >> (I believe it is impossible to remove all previous versions without
> >> re-building the repository, but what
> >> about simply removing it from now on?)
> >
> >
> >
> > copy file elsewhere
> > svn rm file
> > svn commit file
> > copy file back from elsewhere
> >
>
> --
> Donald H Locker
> PTM Electronics, Inc
> 734 426 9010
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
Received on Mon Aug 21 13:56:53 2006