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

down with rollback! (was: svn commit: rev 2162 - trunk/subversion/clients/cmdline trunk/subversion/tests/clients/cmdline/getopt_tests_data)

From: Greg Stein <gstein_at_lyra.org>
Date: 2002-06-13 00:22:17 CEST

On Wed, Jun 12, 2002 at 03:37:19PM -0500, Karl Fogel wrote:
> Garrett Rooney <rooneg@electricjellyfish.net> writes:
> > this is certainly a possibility. what do people think?
> >
> > is it worth it to have this command at all? i'm perfectly willing to
> > just 'svn rm' the file and be done with it if we'd rather just have
> > people learn to use 'svn merge' to do what they want.
> I think this confusion is a clue -- let's not have it.
> I was originally for it, but the confusion between the two possible
> interpretations of "rollback"'s meaning makes me recant. If people
> just use merge instead, they'll always know what they're getting.

After reading through this thread... yes, I'm of a similar mind.

  --> Rollback and merge are "two ways to say the same thing"

Being of a Python mindset rather than Perl, I see that as Badness(tm)

So... count me as a -0.5 on a 'svn rollback' command. There have been a
couple use cases for rollback detailed on this thread. Just put those into a
"simple recipe" cookbook of SVN tasks.

  "to reverse the changes of rev R in your WC, do ..."
  "to return your working copy to rev R (as local mods), do ..."


Greg Stein, http://www.lyra.org/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jun 13 00:21:05 2002

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