From: Dmitry Gutov <dgutov@yandex.ru>
To: Glenn Morris <rgm@gnu.org>, 19548@debbugs.gnu.org
Cc: "Eric S. Raymond" <esr@thyrsus.com>
Subject: bug#19548: VC changes under-documented, needlessly incompatible
Date: Mon, 16 May 2016 02:37:33 +0300 [thread overview]
Message-ID: <4cbd510d-80a3-276a-3d80-0a80c8e8143d@yandex.ru> (raw)
In-Reply-To: <ae53802a-1ba0-8797-a033-58658394c1e6@yandex.ru>
On 05/09/2016 02:42 AM, Dmitry Gutov wrote:
> Why don't we remove vc-stay-local instead, and keep the appropriately
> named vc-cvs-stay-local?
>
> Do we expect vc-stay-local to have been a lot more popular to customize?
> Then indeed it can become an alias.
On the other hand, vc-cvs-stay-local-p contains this bit of code:
(let* ((sym (vc-make-backend-sym 'CVS 'stay-local))
(stay-local (if (boundp sym) (symbol-value sym) vc-stay-local)))
which seems like it will ensure that if the user has customized both
vc-stay-local and vc-cvs-stay-local, the latter will win out (which
won't necessarily happen if we just declare the former to be an obsolete
alias of the latter).
So it seems we're actually buying some extra compatibility here at the
cost of some complexity. Do we care about the above detail?
If yes, vc-stay-local should remain as it is now. If not, I'll gladly
rename it back to vc-cvs-stay-local, and create an obsolete alias.
next prev parent reply other threads:[~2016-05-15 23:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 17:41 bug#19548: VC changes under-documented, needlessly incompatible Glenn Morris
2016-05-08 23:42 ` Dmitry Gutov
2016-05-13 21:05 ` Glenn Morris
2016-05-14 7:41 ` Eli Zaretskii
2016-05-15 23:37 ` Dmitry Gutov [this message]
2016-05-23 17:37 ` Eli Zaretskii
2016-05-23 23:07 ` Dmitry Gutov
2016-05-24 15:34 ` Eli Zaretskii
2016-05-25 1:06 ` Dmitry Gutov
2016-05-23 17:36 ` Eli Zaretskii
2016-05-23 22:49 ` Dmitry Gutov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4cbd510d-80a3-276a-3d80-0a80c8e8143d@yandex.ru \
--to=dgutov@yandex.ru \
--cc=19548@debbugs.gnu.org \
--cc=esr@thyrsus.com \
--cc=rgm@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.