On Wed, Jun 12, 2002 at 03:22:17PM -0700, Greg Stein wrote:
> 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 ..."
ok, you guys convinced me, i've removed it in revision 2178.
someone else can write the cookbook ;-)
-garrett
--
garrett rooney Remember, any design flaw you're
rooneg@electricjellyfish.net sufficiently snide about becomes
http://electricjellyfish.net/ a feature. -- Dan Sugalski
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jun 13 04:07:21 2002