From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>, Manuel Giraud <manuel@ledu-giraud.fr>
Cc: 50572@debbugs.gnu.org
Subject: bug#50572: 28.0.50; [PATCH] fix VC to find the responsible backend with the most specific path.
Date: Wed, 15 Sep 2021 13:41:57 +0300 [thread overview]
Message-ID: <143cbf9a-ff56-150a-6610-bfa9f2c05600@yandex.ru> (raw)
In-Reply-To: <83h7encrq1.fsf@gnu.org>
On 14.09.2021 14:38, Eli Zaretskii wrote:
>> FWIW, I think the most specific should be the default of
>> "C-x v v"
> I'm worried that we are arbitrarily changing the defaults, for the
> sole reason that the new default plays better with someone's
> workflows. AFAIR, it used to be the case that the order of VCS names
> in vc-handled-backends determined the way the default is sought out
> and set. This change (and I think the other one Dmitry mentioned in
> his response?) change that in a way that doesn't leave any "fire
> escape" to users who might be setting things up to have a meaningful
> (for them) order in that list.
It's really more of a discussion for bug#42966. Because no matter how
one feels about that change (I don't have a strong opinion), these two
pieces of code should follow the same pattern.
Now, the change in vc-responsible-backend might seem controversial, as
it decreases customizability and performance (a bit), but it was made a
year ago, and we've received no substantial complaints. And there have
been multiple reports (all linked) about the previous behavior.
next prev parent reply other threads:[~2021-09-15 10:41 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 15:47 bug#50572: 28.0.50; [PATCH] fix VC to find the responsible backend with the most specific path Manuel Giraud
2021-09-13 16:10 ` Eli Zaretskii
2021-09-13 23:48 ` Dmitry Gutov
2021-09-14 2:28 ` Eli Zaretskii
2021-09-14 7:57 ` Manuel Giraud
2021-09-14 7:50 ` Manuel Giraud
2021-09-14 11:38 ` Eli Zaretskii
2021-09-14 12:08 ` Manuel Giraud
2021-09-14 12:57 ` Eli Zaretskii
2021-09-14 15:15 ` Manuel Giraud
2021-09-14 16:03 ` Eli Zaretskii
2021-09-15 9:17 ` Manuel Giraud
2021-09-15 10:35 ` Dmitry Gutov
2021-09-15 11:20 ` Eli Zaretskii
2021-09-15 11:36 ` Dmitry Gutov
2021-09-15 10:41 ` Dmitry Gutov [this message]
2021-09-15 11:22 ` Eli Zaretskii
2021-09-15 11:37 ` Dmitry Gutov
2021-09-15 11:44 ` Eli Zaretskii
2021-09-15 11:47 ` Dmitry Gutov
2021-09-16 12:55 ` Lars Ingebrigtsen
2021-11-06 0:16 ` Lars Ingebrigtsen
2021-11-06 15:01 ` Andy Moreton
2021-11-06 18:19 ` Lars Ingebrigtsen
2021-11-06 22:30 ` Andy Moreton
2021-11-06 22:35 ` Dmitry Gutov
2021-11-07 13:17 ` Lars Ingebrigtsen
2021-11-08 9:28 ` Manuel Giraud
2021-11-08 9:31 ` Lars Ingebrigtsen
2021-11-08 10:37 ` Manuel Giraud
2021-11-09 3:29 ` Lars Ingebrigtsen
2021-11-09 8:09 ` Juri Linkov
2021-11-09 22:55 ` Lars Ingebrigtsen
2021-11-09 8:51 ` Manuel Giraud
2021-11-09 23:30 ` Lars Ingebrigtsen
2021-11-10 0:06 ` Dmitry Gutov
2021-11-10 0:20 ` Lars Ingebrigtsen
2021-11-10 0:29 ` Dmitry Gutov
2021-11-10 0:39 ` Lars Ingebrigtsen
2021-11-10 12:54 ` Eli Zaretskii
2021-11-10 12:59 ` Lars Ingebrigtsen
2021-11-10 14:23 ` Eli Zaretskii
2021-11-11 2:56 ` Lars Ingebrigtsen
2021-11-11 7:06 ` Eli Zaretskii
2021-11-11 7:46 ` Michael Albinus
2021-11-11 8:04 ` Eli Zaretskii
2021-11-11 10:46 ` Michael Albinus
2021-11-11 12:21 ` Lars Ingebrigtsen
2021-11-11 15:09 ` Eli Zaretskii
2021-11-12 3:01 ` Lars Ingebrigtsen
2021-11-12 9:51 ` Manuel Giraud
2021-11-12 12:05 ` Eli Zaretskii
2021-11-12 15:09 ` Manuel Giraud
2021-11-12 15:20 ` Eli Zaretskii
2021-11-12 15:41 ` Manuel Giraud
2021-11-12 19:21 ` Manuel Giraud
2021-11-12 19:40 ` Eli Zaretskii
2021-11-14 0:51 ` Lars Ingebrigtsen
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=143cbf9a-ff56-150a-6610-bfa9f2c05600@yandex.ru \
--to=dgutov@yandex.ru \
--cc=50572@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=manuel@ledu-giraud.fr \
/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).