From: Corwin Brust <corwin@bru.st>
To: Justin Burkett <justin@burkett.cc>
Cc: Stefan Kangas <stefan@marxist.se>, Ergus <spacibba@aol.com>,
Stephen Leake <stephen_leake@stephe-leake.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: Include which-key.el in the Emacs distribution
Date: Sun, 13 Feb 2022 21:46:15 -0600 [thread overview]
Message-ID: <CAJf-WoTCTczHV_E9=w+Fx9woSSH6Pze=rNfaEOy8DXS78RQOAA@mail.gmail.com> (raw)
In-Reply-To: <CAF5dqNLKtnL9Dz4YmoMEwWCZQR2ZTxwhUza_K7iuOnLjhFxonQ@mail.gmail.com>
I'd be happy to help if a "warm body" to "do stuff" is what's needed.
On Sun, Feb 13, 2022 at 9:09 PM Justin Burkett <justin@burkett.cc> wrote:
>
> 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 <monnier@iro.umontreal.ca> 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
>>
next prev parent reply other threads:[~2022-02-14 3:46 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 13:54 Include which-key.el in the Emacs distribution Stefan Kangas
2020-09-08 14:01 ` Ergus
2020-09-08 14:16 ` Stefan Kangas
2020-09-08 17:29 ` Yuan Fu
2020-09-08 17:40 ` Justin Burkett
2020-09-08 20:40 ` Stefan Kangas
2020-09-08 16:22 ` Alfred M. Szmidt
2020-09-08 17:24 ` Eli Zaretskii
2020-09-08 17:37 ` Amin Bandali
2020-09-08 17:51 ` Alfred M. Szmidt
2020-09-08 17:54 ` Justin Burkett
2020-09-08 18:06 ` Eli Zaretskii
2020-09-08 18:11 ` Justin Burkett
2020-09-08 20:40 ` Stefan Kangas
2020-09-08 18:10 ` Alfred M. Szmidt
2020-09-08 18:00 ` Eli Zaretskii
2020-09-08 19:12 ` Amin Bandali
2020-09-08 18:25 ` Caio Henrique
2020-09-08 19:19 ` Stefan Monnier
2020-09-08 20:14 ` Ergus
2020-09-08 20:40 ` Stefan Kangas
2022-02-11 21:31 ` Corwin Brust
2022-02-13 17:30 ` Philip Kaludercic
2022-02-14 9:04 ` Pankaj Jangid
2022-02-14 16:23 ` [External] : " Drew Adams
2022-02-14 22:09 ` Tim Cross
2022-02-13 17:59 ` Stephen Leake
2022-02-13 18:17 ` Corwin Brust
2022-02-13 23:25 ` Stephen Leake
2022-02-14 2:47 ` Stefan Monnier
2022-02-14 3:09 ` Justin Burkett
2022-02-14 3:46 ` Corwin Brust [this message]
[not found] <<CADwFkmmvVRqnQGA_d8bMA66SXbpjis+j-1UiceY7Lk7eY6iugA@mail.gmail.com>
[not found] ` <<E1kFgO6-0000cE-Dj@fencepost.gnu.org>
2020-09-08 17:55 ` Drew Adams
[not found] ` <<83sgbskwq8.fsf@gnu.org>
2020-09-08 18:05 ` Drew Adams
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='CAJf-WoTCTczHV_E9=w+Fx9woSSH6Pze=rNfaEOy8DXS78RQOAA@mail.gmail.com' \
--to=corwin@bru.st \
--cc=emacs-devel@gnu.org \
--cc=justin@burkett.cc \
--cc=monnier@iro.umontreal.ca \
--cc=spacibba@aol.com \
--cc=stefan@marxist.se \
--cc=stephen_leake@stephe-leake.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 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).