[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Backing out changes: the prefered method?

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2002-01-31 00:22:25 CET

Greg Hudson <ghudson@MIT.EDU> writes:

> On Wed, 2002-01-30 at 17:37, Sean Russell wrote:
> > It may be beyond the scope of the first release, but like I said: being able
> > to configure, at compile time, which behavior you have enabled would be a
> > Good Thing.
> That would be awful. Unless I built my svn client myself, I wouldn't
> know which behavior I'd be getting. A distributor would never be sure
> which behavior to enable by default. And so on.
> "svn rollback" should commit a reversion. "svn destroy-history" or
> something suitably clear should remove revisions from history,
> presumably at the regrettable expense of working directories which are
> at the obsoleted revisions (just as with cvs admin -o).

I would not like to see "svn destroy-history" under any circumstances.
I wouldn't want the ra_dav layer to support it either, as I don't want
someone writing their own client to enable the behaviour. However I
realise this function needs to be available. The logical place to put
it is in svnadmin, which already contains the setlog command. Then the
destructive behaviour is limited to those that have direct access to
the repository database.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:37:01 2006

This is an archived mail posted to the Subversion Dev mailing list.