Re: Obliterate and auditability

On Mon, Apr 21, 2008 at 4:17 PM, Garance A Drosihn <drosih_at_rpi.edu> wrote:
> At 10:10 AM -0400 4/21/08, John Peacock wrote:
>
> > C. Michael Pilato wrote:
> >
> > > I say that Subversion shouldn't bother with dropping revisions,
> > > should record obliterations as revision properties, and that's that.
> > >
> >
> > +1
> >
> >
> > > But I resonate with those who believe that auditability as a goal
> > > runs closer to the spirit of what a version control tool is than
> > > does the untraceable disposal of versioned data.
> > >
> >
> > <aol>me too!</aol>
> >
>
> +1 for me on these comments. And since I don't say much on this
> mailing list, let me note that I am a person who *does* want an
> official easy way to 'Obliterate' a previously-commited revision.
> But I don't think we need to obliterate the fact that the revision
> ever existed.

Likewise from me. We wouldn't care if the changeset shrank or became
empty. I don't care either way about logs mentioning it. If a log
didn't mention it, I'd probably edit svn:log to make an explicit note,
depending on the circumstances.

Obliterating the data is a separate issue versus hiding the history.
We (freebsd.org) need the former functionality. Doing a dump, edit,
restore is extremely unpleasant, but would get us by in a pinch.
Making this less painful would be a fantastic improvement and would be
well worth having as an available tool - hopefully one never used.

-- 
Peter Wemm - peter_at_wemm.org; peter_at_FreeBSD.org; peter_at_yahoo-inc.com
"All of this is for nothing if we don't go to the stars" - JMS/B5
"If Java had true garbage collection, most programs would delete
themselves upon execution." -- Robert Sewell
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org