From: John Wiegley <jwiegley@gmail.com>
To: Artur Malabarba <bruce.connor.am@gmail.com>
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>,
Alexey Veretennikov <alexey.veretennikov@gmail.com>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: [ELPA] New package: loccur
Date: Wed, 30 Dec 2015 16:20:32 -0800 [thread overview]
Message-ID: <m2lh8bh3jj.fsf@newartisans.com> (raw)
In-Reply-To: <CAAdUY-+aTv_QrJdMeMUnYp4URt0WpROFJroBqqeXvLQ6HDE6YA@mail.gmail.com> (Artur Malabarba's message of "Wed, 30 Dec 2015 20:41:09 -0200")
>>>>> Artur Malabarba <bruce.connor.am@gmail.com> writes:
> What about "Packages which core does not depend on go into ELPA."? :-)
I have a feeling some core packages will decide to depend on async. I can see
Gnus and smtpmail and dired and several others using it, as they already do in
extension modules for those packages out on the Web.
However, until the dependency actually exists in Emacs core, I'd be fine with
it being in ELPA. It should properly go into ELPA until the day when the rest
of core needs it not to be.
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
next prev parent reply other threads:[~2015-12-31 0:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 21:08 [ELPA] New package: loccur Alexey Veretennikov
2015-12-30 21:10 ` John Wiegley
2015-12-30 23:27 ` Alexey Veretennikov
2015-12-30 21:22 ` Marcin Borkowski
2015-12-30 21:29 ` John Wiegley
2015-12-30 21:32 ` Lars Magne Ingebrigtsen
2015-12-30 21:39 ` John Wiegley
2015-12-30 22:41 ` Artur Malabarba
2015-12-31 0:20 ` John Wiegley [this message]
2015-12-31 5:57 ` CHENG Gao
2015-12-31 8:49 ` Michael Albinus
2015-12-31 9:36 ` CHENG Gao
2015-12-31 14:38 ` Rasmus
2015-12-31 0:30 ` Juri Linkov
2015-12-31 3:14 ` daniel sutton
2015-12-31 12:49 ` Alexey Veretennikov
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=m2lh8bh3jj.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=alexey.veretennikov@gmail.com \
--cc=bruce.connor.am@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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).