From: Andrew Hyatt <ahyatt@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Inclusion of websocket library
Date: Fri, 12 Jul 2013 01:29:32 -0400 [thread overview]
Message-ID: <CAM6wYYKbjrEfNcvHr2_s6vADX=JQDJa+L2OvY9iJ7p6S5Qupog@mail.gmail.com> (raw)
In-Reply-To: <jwvy59ekeab.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 944 bytes --]
What is involved is putting this on GNU ELPA? I can certain do that, and
maintain it there, but since my package is already available via Marmalade,
it is already available via an ELPA that (I think) most ELPA-users are
using. Is there a further advantage to putting this on the GNU ELPA
specifically?
On Wed, Jul 10, 2013 at 4:32 AM, Stefan Monnier <monnier@iro.umontreal.ca>wrote:
> > I'm wondering if it anyone thinks this should just be part of the emacs
> > distribution (probably under the "net" directory). I personally think
> that
> > library-type modules such as this should just be included in emacs, but
> > there isn't anything particularly wrong with it being available via ELPA
> as
> > it is now.
>
> It sounds like something that should definitely be in GNU ELPA if you're
> willing to maintain it from there. Maybe even in Emacs proper, tho I'd
> have to think a bit more about it.
>
>
> Stefan "out of town"
>
[-- Attachment #2: Type: text/html, Size: 1357 bytes --]
next prev parent reply other threads:[~2013-07-12 5:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 3:12 Inclusion of websocket library Andrew Hyatt
2013-07-10 8:32 ` Stefan Monnier
2013-07-12 5:29 ` Andrew Hyatt [this message]
2013-07-12 7:08 ` Bozhidar Batsov
2013-07-31 4:25 ` Stefan Monnier
2013-07-31 13:56 ` Andrew Hyatt
2013-07-31 17:55 ` Stefan Monnier
2013-08-01 15:11 ` Andrew Hyatt
2013-08-01 18:24 ` Stefan Monnier
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='CAM6wYYKbjrEfNcvHr2_s6vADX=JQDJa+L2OvY9iJ7p6S5Qupog@mail.gmail.com' \
--to=ahyatt@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).