[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: Sean Russell <ser_at_germane-software.com>
Date: 2002-01-30 22:12:15 CET

Hash: SHA1

On Wednesday 30 January 2002 10:59, Ben Collins-Sussman
and Sander Striker wrote:
> > But I think garrett was talking about people who want to actually
> > remove all history of the change from the server. That's a much
> Ah. I'd like to hear some arguments in favor of that. At first
> glance I feel very negative towards having rollback remove all traces
> of a commit completely.

I would argue that you should be able to disable any "change history"
functionality. I'm especially concerned about audit trails; if you allow svn
clients to change history, you remove a number of valid uses for SVN.

Our company, for example, needs to have audit trails for timesheets, which
are electronic. At the moment, we just print out the timesheets and file
them. We'd like to back up the databases by dumping them, and then commiting
them to CVS or SVN. We're investigating a number of ways of ensuring the
audit trail in a way that satisfies the govornment standards. If SVN allowed
changing history, it would make it useless for this.

- - --

 |.. "Intel: putting the 'backward' in 'backward compatible'..."
<|> -- anon
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org


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.