Re: the obliterate discussion - why dumpfiltering is no valid workaround

patrick wrote:
>
> i'm not stupid. i can see that the revisions depend on each other. but i can
> also see that erasing a whole file (not just the changes of one revision) is
> not a difficult task. find the root where it was added, remove it and then
> go trough the history and remove all future referecnes to this file.
> i could write a java app which does it in the dumpfiles if i had to. it
> would be slow...

Until a better solution is implemented, I think everyone should consider
this scenario whenever the question comes up about putting everything in
one big repository or splitting projects into separate repositories.
Under the principle that 'anything that can go wrong, will', it's just a
matter of time before someone will commit something that for reasons of
space, legality, or just bad taste, can't stay there and you'll have to
deal with the time and space it takes to go though the dump and filter
process. If that's going to be difficult with everything in one
repository, perhaps they should never be put together in the first place.

-- 
   Les Mikesell
    lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org