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

"svn obliterate" (was: RE: Backing out changes: the prefered method?)

From: Frohwalt Egerer <mail_at_frohwalt.de>
Date: 2002-01-31 01:17:30 CET

> -----Original Message-----
> From: Greg Hudson [mailto:ghudson@MIT.EDU]
> Sent: Mittwoch, 30. Januar 2002 23:45
> To: Sean Russell
> Cc: dev@subversion.tigris.org
> Subject: Re: Backing out changes: the prefered method?


> "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).

This is exactly what perforce does, and it is quite sane IMHO. To remove
something from the repository you type

p4 obliterate filespec

where filespec can be one or more revisions of some file.

So this is my +1 on "svn obliterate"

Since our team uses PVCS (*) the Perforce repo on my machine is for "private
temporary use" only (and to ease my pain of using PVCS). So I regularily
obliterate everything which is older than a few months. (Anybody needs a
python script which does a CVS-like "commit" with PVCS? ;-)

Frohwalt Egerer

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.