Thanks for the extended thread here. I do not mean to be glib about the
potential complexities of implementing this (as hinted by Max Bowsher). I
was not thinking of this being a user command, either. It's just that
management has wondered about reducing repository size, and I've found that
svndumpfilter is tricky when you're trying to exclude something that was also
"svn copied" (or moved) to somewhere else. One of the reasons we switched to
svn was the tracking of history across moves/copies. This has a price in
complexity when you start wanting to "remove" things.
> -----Original Message-----
> From: Marc Haisenko [mailto:haisenko@webport.de]
> Sent: Monday, January 31, 2005 11:25 AM
> To: users@subversion.tigris.org
> Subject: Re: Is anyone working on "svn obliterate"?
>
>
> On Monday 31 January 2005 16:59, William Nagel wrote:
> > > Out of even more curiosity, what does it do??? I'm just a user &
> > > have no idea what it is...
> >
> > I think the idea is that you'd be able to run "svn obliterate" and
> > completely remove a file from previous revisions.
> >
> > Seems like an extremely dangerous activity to be able to do with a
> > simple client-level command.
>
> I totally agree ! Every action by an user can be undone, but
> this command
> would not be undoable and thus is so dangerous that it
> shouldn't be given to
> the users hands. And the admin can delete a file with snvdumpfilter.
>
> C'ya,
> Marc
> --
> Marc Haisenko
> Systemspezialist
> Webport IT-Services GmbH
> mailto: haisenko@webport.de
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jan 31 18:03:50 2005