[Top][All Lists]

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

Re: RCS: (vc-next-action 1) only New Backend

From: Dmitry Gutov
Subject: Re: RCS: (vc-next-action 1) only New Backend
Date: Sat, 19 Sep 2015 20:41:33 +0300
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 Thunderbird/41.0

On 09/19/2015 08:35 PM, Eli Zaretskii wrote:

Without this capability, you are forever limited to the 1.x series of
revisions, with the 1 part fixed and the x part monotonously
increasing ad nauseam.  With this feature available, the user can
start with version 0.1, proceed to 0.99, then decide the software is
mature enough to be called 1.0, then bump to 2.0 when some major
feature is added, etc.  Since revision numbers in RCS and similar
VCSes served also as poor man's version tags, not having this ability
takes away an important feature with these VCSes.

I see, thank you for the explanation.

I cannot in good faith call the removal of a (now optional) argument a
"cleanup", sorry.  Given the importance of the lost functionality, it
just isn't worth it, IMO.

It *did* make the API better, somewhat.

In case someone has the time to try out a better fix, maybe this feature would be better to implement the "assign the revision" functionality in a backend-specific way, via a MIME header in the log-edit buffer, the same way as we specify "Amend" in Git, or "Author" in most backends.

reply via email to

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