unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: timo.myyra@bittivirhe.fi, op@omarpolo.com, emacs-devel@gnu.org
Subject: Re: [elpa] New package: vc-got
Date: Tue, 31 Aug 2021 16:55:10 +0300	[thread overview]
Message-ID: <fb5838a0-e2fd-451c-6022-a0fabbe360d3@yandex.ru> (raw)
In-Reply-To: <83sfypsp34.fsf@gnu.org>

On 31.08.2021 16:47, Eli Zaretskii wrote:
>> Cc: op@omarpolo.com, timo.myyra@bittivirhe.fi, emacs-devel@gnu.org
>> From: Dmitry Gutov <dgutov@yandex.ru>
>> Date: Tue, 31 Aug 2021 16:46:05 +0300
>>
>> On 31.08.2021 16:41, Eli Zaretskii wrote:
>>> So you are saying it doesn't have a place even on ELPA?
>>
>> Sure it has: the ELPA packages don't have to be 100% practical.
> 
> Really?  I'm surprised.

Surely even you can agree that criteria for ELPA and core shouldn't be 
the same.

>> If people want to use got, they might enjoy a dedicated VC backend for it.
> 
> So I'm asking if, for the same reason, it could make sense to have it
> in core.

Aside from "why not?" not being a good reason, since 
2697123933e3ac7ed4e21a6d12746a98ed7fa74a vc-responsible-backend iterates 
through all enabled backends when choosing the "current" one. So the 
longer we make the list of built-in backends, the more overhead we get 
on this.



  reply	other threads:[~2021-08-31 13:55 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-31 10:17 [elpa] New package: vc-got Omar Polo
2021-08-31 13:10 ` Eli Zaretskii
2021-08-31 13:31   ` Dmitry Gutov
2021-08-31 13:41     ` Eli Zaretskii
2021-08-31 13:46       ` Dmitry Gutov
2021-08-31 13:47         ` Eli Zaretskii
2021-08-31 13:55           ` Dmitry Gutov [this message]
2021-08-31 14:00             ` Eli Zaretskii
2021-08-31 14:02               ` Dmitry Gutov
2021-08-31 14:07                 ` Eli Zaretskii
2021-08-31 14:08                 ` Eli Zaretskii
2021-08-31 14:21                   ` Stefan Kangas
2021-08-31 15:37                     ` Eli Zaretskii
2021-10-17  4:57               ` Jean Louis
2021-10-17  6:21                 ` Eli Zaretskii
2021-10-17  7:33                   ` Jean Louis
2021-10-17 10:02                     ` Eli Zaretskii
2021-10-17 10:13                     ` Omar Polo
2021-08-31 14:00     ` Omar Polo
2021-08-31 14:34       ` Dmitry Gutov
2021-08-31 14:38         ` Omar Polo
2021-08-31 15:38       ` Eli Zaretskii
2021-08-31 14:44   ` Dmitry Gutov
2021-08-31 15:40     ` Eli Zaretskii
2021-08-31 13:32 ` Philip Kaludercic
2021-08-31 13:59   ` Omar Polo
2021-08-31 16:54     ` Philip Kaludercic
2021-09-09 15:50     ` Philip Kaludercic

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=fb5838a0-e2fd-451c-6022-a0fabbe360d3@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=op@omarpolo.com \
    --cc=timo.myyra@bittivirhe.fi \
    /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).