Re: feature proposal: svn:maxrevs

On Tuesday 23 March 2004 10:08 am, Ben Collins-Sussman wrote:
> On Tue, 2004-03-23 at 10:01, McClain Looney wrote:
>
> But what you've proposed is a UI... I think the harder problem to tackle
> here is the implementation. Exactly *how* do we make libsvn_fs lose
> data? The 'svn obliterate' issue (#516) begins to discuss this
> problem. Talking about UIs before hde database implementation, I think,
> is putting the cart before the horse.

nah, it just looked like i was proposing just the ui. not being a c guy, i
have no idea what to propose to actually implement it. i guess it could be
restated as automated svn obliterate.

it occurrs to me that the ripple effecty might be mitigatable by replacing the
historical (now deleted) nodes with pointers to the next available revision.
or is it unacceptable to suddenly have historical revisions pointing to
different resources all of the sudden?

-- 
McClain Looney
LoonSoft LLC
m@loonsoft.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org