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

Re: svn commit: r25763 - trunk/subversion/libsvn_client

From: Daniel Rall <dlr_at_collab.net>
Date: 2007-07-18 01:36:53 CEST

On Mon, 16 Jul 2007, Blair Zajac wrote:

> C. Michael Pilato wrote:
> >dlr@tigris.org wrote:
> >>Author: dlr
> >>Date: Mon Jul 16 17:45:21 2007
> >>New Revision: 25763
> >>
> >>Log:
> >>Change "revert" terminology to "rollback" throughout to differentiate
> >>between Subversion's 'revert' subcommand and a subtractive 'merge'.
> >
> >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?
> Well, I would guess that people coming from a database background will
> think of rollbacks the way you describe them.
> Why don't we call them reverse merges? There's no ambiguity there.

Yup. Just seemed a little long for a variable name...

  • application/pgp-signature attachment: stored
Received on Wed Jul 18 01:36:02 2007

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.