[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: RCS, again: another removed functionality: undo last-checkin

From: Eli Zaretskii
Subject: Re: RCS, again: another removed functionality: undo last-checkin
Date: Mon, 21 Sep 2015 22:53:00 +0300

> Cc: address@hidden, address@hidden
> From: Dmitry Gutov <address@hidden>
> Date: Mon, 21 Sep 2015 22:33:42 +0300
> On 09/21/2015 10:17 PM, Eli Zaretskii wrote:
> > Yes, it does.  From the description of "cvs admin":
>  > ...
> >    `-oRANGE'
> >         Deletes ("outdates") the revisions given by RANGE.
> >
> > (It then goes on to describe the syntax of RANGE, basically
> > REV1::REV2.)
> Can it remove revisions from the tip, too?


> >> 'git revert', by itself, doesn't affect the remote either.
> >
> > Indeed, so what is the reason not to use it as "rollback"?
> Like it's been said, 'rcs rollback' removes a revision from history 
> (right?). 'git revert' doesn't.

Because it's impossible.  But it does the closest thing possible.

> That's an inconsistency that can be surprising for a user.

I don't see this as an argument not to have the capability.

> Otherwise, 'git reset' and 'git revert' are roughly equivalent in this 
> regard. It's just that 'git push' will fail upon being called after the 
> former, in certain circumstances.

The idea of the proposal, namely, call 'revert' when 'reset' followed
by 'push' would fail, was to avoid the failure.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]