From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Justin Burkett Newsgroups: gmane.emacs.devel Subject: Re: Include which-key.el in the Emacs distribution Date: Sun, 13 Feb 2022 22:09:05 -0500 Message-ID: References: <20200908201434.hrvupafbu2kyvb4q@Ergus> <86pmnqabr3.fsf@stephe-leake.org> <86leye9wn8.fsf@stephe-leake.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000ca4a5905d7f1be29" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="20798"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Stefan Kangas , Ergus , Corwin Brust , Stephen Leake , Emacs developers To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Feb 14 04:11:05 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nJRlY-0005E4-Ng for ged-emacs-devel@m.gmane-mx.org; Mon, 14 Feb 2022 04:11:04 +0100 Original-Received: from localhost ([::1]:42514 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nJRlX-0002Bq-4x for ged-emacs-devel@m.gmane-mx.org; Sun, 13 Feb 2022 22:11:03 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:53178) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nJRk9-0001U1-BC for emacs-devel@gnu.org; Sun, 13 Feb 2022 22:09:37 -0500 Original-Received: from [2607:f8b0:4864:20::835] (port=39785 helo=mail-qt1-x835.google.com) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nJRk7-0007pn-3g for emacs-devel@gnu.org; Sun, 13 Feb 2022 22:09:37 -0500 Original-Received: by mail-qt1-x835.google.com with SMTP id e16so14419725qtq.6 for ; Sun, 13 Feb 2022 19:09:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=burkett-cc.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=gh/U+ogzaLRodVSzaQBwdflMc6L7P56TCM39dS6+0Ss=; b=esCkYVI9eRxSc1mHjEwFq6GnIURzbVhOnXymA9Zi5o2z7Ca4ghhHnYAp5ie4oK0t+I NSY8zQyrvlQIaSIvoon4grUmfQnHd217y7oWz3bg+W+4+al6QI4Kmza93JBhj3F0HWj9 RGnGmjYB9rFDE1PKIV35zrykDyH9F+T8mUBjwbYEdeHmFWy7zDenFHeUuRUnUo+O5gCG rJPlBw6pN6WQJCy9ObKVpZbPTwlP5zCRfhwN9+ZDgrUfysQZm/sCp/YL6laKFNm7jFiI 63w/Nyy2CvqrrPwm0F2pQEsDhx5YpLsHuDDjphoBC0jX3WfIdF9DB0H2toMupaIgX7XA G4Wg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=gh/U+ogzaLRodVSzaQBwdflMc6L7P56TCM39dS6+0Ss=; b=qH2sqW/qDQVm8epZzoJDMYd5U585ouPeIjuWNp8rWvXpRaQjk2CjxGNzme3+US15Xc T3On/EJIHpP2oq6TXAfVKb5+47c4f2n1ZHDf1GPFJ+tXYvhZc5k1hJ9Y/Ep+SUAqlakq 1cb1n5yXqZpInHUZ+fvmVNo9rS2SrOA8nOIMzoL7uvTTvINsDSLb7A6NsNgGfx+idpgq 5k0WgS2vxA3HRnFYzNP/TPi0WY7R5rwdXvZ2z4QVthWdU5r9W0uiMYb1ygVS0NekSlL2 g5SZ5NIavOGTNbc7DlKl16L6wEXFwGCyrH7Gse6nCh4LQjXnxotBZ7PkGBHKrdfs32SN HZoQ== X-Gm-Message-State: AOAM530e7oMVVksz/iiHBvczqPzm5+ZQM8oLJkhcIG8EdS9Y2ZJktJWV xB37xmHdCZEGThUo7CfLIiG1KlM9YW7HxQMG X-Google-Smtp-Source: ABdhPJwrYzhU5VfjLEtkLvcOe69naqJ6+skWmsRHgQqRpzGJOqpmP70104ZCjVf/sJAC2fAPOp6yHA== X-Received: by 2002:ac8:5dd0:: with SMTP id e16mr8267731qtx.521.1644808173426; Sun, 13 Feb 2022 19:09:33 -0800 (PST) Original-Received: from mail-qt1-f177.google.com (mail-qt1-f177.google.com. [209.85.160.177]) by smtp.gmail.com with ESMTPSA id h6sm15288626qko.7.2022.02.13.19.09.31 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 13 Feb 2022 19:09:31 -0800 (PST) Original-Received: by mail-qt1-f177.google.com with SMTP id y8so14388659qtn.8 for ; Sun, 13 Feb 2022 19:09:31 -0800 (PST) X-Received: by 2002:a05:622a:54d:: with SMTP id m13mr8441255qtx.106.1644808171569; Sun, 13 Feb 2022 19:09:31 -0800 (PST) In-Reply-To: X-Gmail-Original-Message-ID: X-Host-Lookup-Failed: Reverse DNS lookup failed for 2607:f8b0:4864:20::835 (failed) Received-SPF: none client-ip=2607:f8b0:4864:20::835; envelope-from=justin@burkett.cc; helo=mail-qt1-x835.google.com X-Spam_score_int: -2 X-Spam_score: -0.3 X-Spam_bar: / X-Spam_report: (-0.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, PDS_HP_HELO_NORDNS=0.785, RCVD_IN_DNSWL_NONE=-0.0001, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:286229 Archived-At: --000000000000ca4a5905d7f1be29 Content-Type: text/plain; charset="UTF-8" I don't have anything to say about the process of moving it into the core, but it's fine with me if you all decide to do that. I don't have much time these days to contribute, however. Justin On Sun, Feb 13, 2022 at 9:47 PM Stefan Monnier wrote: > > That's easy; there is a lisp/erc directory in the master emacs git > > repository. Apparently someone syncs the code between there and ELPA. > > Not really: the GNU ELPA packages are generated from code kept in the > `elpa.git` repository, but it can also use the code in Emacs itself > (i.e. in the `master` branch of the `emacs.git` repository), which is > what happens for ERC, Python, and a few more, whose "upstream" is > Emacs's own repository. > > > There are also "core" ELPA packages; the code resides in the emacs > > master repository, but the ELPA server also packages it. I think the > > only examples of those are single-file, but it should work for > > multi-file as well. > > It's not limited to single-file packages. > The ERC package is one of those. > > > Stefan > > --000000000000ca4a5905d7f1be29 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I don't have anything to say about the process of movi= ng it into the core, but it's fine with me if you all decide to do that= . I don't have much time these days to contribute, however.=C2=A0
<= br>
Justin=C2=A0

On Sun, Feb 13, 2022 at 9:47 PM Stefan Monn= ier <monnier@iro.umontreal.c= a> wrote:
> That's easy; there is a lisp/erc directory in the master emacs gi= t
> repository. Apparently someone syncs the code between there and ELPA.<= br>
Not really: the GNU ELPA packages are generated from code kept in the
`elpa.git` repository, but it can also use the code in Emacs itself
(i.e. in the `master` branch of the `emacs.git` repository), which is
what happens for ERC, Python, and a few more, whose "upstream" is=
Emacs's own repository.

> There are also "core" ELPA packages; the code resides in the= emacs
> master repository, but the ELPA server also packages it. I think the > only examples of those are single-file, but it should work for
> multi-file as well.

It's not limited to single-file packages.
The ERC package is one of those.


=C2=A0 =C2=A0 =C2=A0 =C2=A0 Stefan

--000000000000ca4a5905d7f1be29--