|
From: | Dmitry Gutov |
Subject: | Re: RCS, again: another removed functionality: undo last-checkin |
Date: | Wed, 23 Sep 2015 17:49:44 +0300 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 Thunderbird/41.0 |
On 09/23/2015 09:58 AM, Eli Zaretskii wrote:
With such a difference in back-end implementation of a rollback, it would be appropriate to have a separate back-end method that produces the warning language.
I don't like that very much (sounds complex). Better to have two commands, and allow a backend to signal error in one of them.
But then what will we do with back-ends where there's only one command for a rollback, and it works regardless of whether the the commit was published?
If the backend doesn't know when to signal an error, it won't. The RCS and CVS backend obviously won't do that.
A slight modification on that plan would be a new `revision-public' command which returns t if we're not supposed to modify or rollback that revision. Then the error would be raised not by vc-git, but by generic code.
[Prev in Thread] | Current Thread | [Next in Thread] |