From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: oub@mat.ucm.es, dak@gnu.org, emacs-devel@gnu.org
Subject: Re: RCS: (vc-next-action 1) only New Backend
Date: Sat, 19 Sep 2015 20:41:33 +0300 [thread overview]
Message-ID: <55FD9E4D.8080909@yandex.ru> (raw)
In-Reply-To: <83pp1epb17.fsf@gnu.org>
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.
next prev parent reply other threads:[~2015-09-19 17:41 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 15:39 RCS: (vc-next-action 1) only New Backend Uwe Brauer
2015-09-18 17:18 ` Eli Zaretskii
2015-09-18 20:46 ` Uwe Brauer
2015-09-19 7:00 ` Eli Zaretskii
2015-09-19 8:46 ` Uwe Brauer
2015-09-19 8:59 ` David Kastrup
2015-09-19 9:23 ` Eli Zaretskii
2015-09-19 9:36 ` Uwe Brauer
2015-09-19 10:34 ` Eli Zaretskii
2015-09-19 9:30 ` Eli Zaretskii
2015-09-19 10:00 ` David Kastrup
2015-09-19 10:30 ` Uwe Brauer
2015-09-19 10:40 ` Eli Zaretskii
2015-09-19 10:58 ` David Kastrup
2015-09-19 11:06 ` Eli Zaretskii
2015-09-19 12:29 ` Uwe Brauer
2015-09-19 14:11 ` Eli Zaretskii
2015-09-19 21:15 ` Uwe Brauer
2015-09-19 16:05 ` Dmitry Gutov
2015-09-19 17:35 ` Eli Zaretskii
2015-09-19 17:41 ` Dmitry Gutov [this message]
2015-09-19 17:49 ` Eli Zaretskii
2015-09-19 19:44 ` Dmitry Gutov
2015-09-19 21:14 ` Uwe Brauer
2015-09-19 22:42 ` Dmitry Gutov
2015-09-20 6:08 ` Eli Zaretskii
2015-09-20 13:10 ` Dmitry Gutov
2015-09-20 14:49 ` Eli Zaretskii
2015-09-20 16:27 ` Stefan Monnier
2015-09-20 17:10 ` Eli Zaretskii
2015-09-20 17:15 ` Eli Zaretskii
2015-09-20 19:25 ` Stefan Monnier
2015-09-20 19:40 ` Eli Zaretskii
2015-09-20 20:53 ` Dmitry Gutov
2015-09-21 6:17 ` Eli Zaretskii
2015-09-21 2:18 ` Stefan Monnier
2015-09-21 2:29 ` Dmitry Gutov
2015-09-21 6:59 ` Eli Zaretskii
2015-09-21 14:06 ` Dmitry Gutov
2015-09-21 16:12 ` Eli Zaretskii
2015-09-21 16:48 ` Dmitry Gutov
2015-09-21 16:59 ` Eli Zaretskii
2015-09-21 17:33 ` Dmitry Gutov
2015-09-21 19:21 ` Eli Zaretskii
2015-09-21 5:30 ` David Kastrup
2015-09-21 13:14 ` Stefan Monnier
2015-09-21 7:08 ` Eli Zaretskii
2015-09-20 23:54 ` Dmitry Gutov
2015-09-21 6:52 ` Eli Zaretskii
2015-09-20 6:03 ` Eli Zaretskii
2015-09-19 20:21 ` Stefan Monnier
2015-09-19 9:31 ` Uwe Brauer
2015-09-19 17:29 ` Stefan Monnier
2015-09-19 17:45 ` Eli Zaretskii
2015-09-19 20:18 ` Stefan Monnier
2015-09-20 6:06 ` Eli Zaretskii
2015-09-19 9:21 ` Eli Zaretskii
2015-09-19 9:35 ` Uwe Brauer
2015-09-19 10:34 ` Eli Zaretskii
2015-09-19 10:35 ` Uwe Brauer
2015-09-20 10:05 ` Uwe Brauer
2015-09-20 10:45 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55FD9E4D.8080909@yandex.ru \
--to=dgutov@yandex.ru \
--cc=dak@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=oub@mat.ucm.es \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).