On 7/16/07, Eric S. Raymond <esr@thyrsus.com> wrote:
> C. Michael Pilato <cmpilato@collab.net>:
> > Actually, I'm concerned about the use of the term rollback to mean "any ol'
> > reversal of a changeset". If I'm not mistaken, there are VC system in which
> > rollback means something different, namely the pruning of last N changes to
> > a line of history. In other words, given a file added in r1, changed in r3,
> > r6, and r9, it means nothing to "rollback r6". You can rollback *to* r6 (by
> > reversing r9). You can rollback *to* r1 (by reversing r3, r6, and r9). But
> > rollbacks don't have gaps in them.
> >
> > I can't readily point to documentation of other VC systems to back my claim
> > (which is based entirely on now-fading memories). Am I the only person who
> > thinks of the term "rollback" in this way?
>
> No. New VC mode, following some early VCSes (SCCS, RCS) and some very
> recent ones (notably Mercurial), uses "rollback" in exactly that way.
(To be pedantic, Mercurial doesn't refer to it as "rollback r6" *or*
"rollback to r6" because it supports exactly one revision worth of
rollback: you just "rollback the last transaction". But yeah, it's
more like what cmpilato said than like svnmerge.py rollback.)
--dave
--
David Glasser | glasser_at_mit.edu | http://www.davidglasser.net/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 17 04:38:21 2007