unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Matt DeBoard <matt.deboard@gmail.com>
To: chad <yandros@gmail.com>
Cc: emacs <emacs-devel@gnu.org>
Subject: Re: SMIE
Date: Fri, 15 Aug 2014 21:34:16 -0500	[thread overview]
Message-ID: <CAPLdYOhbxqXf=7YuNFSuSBARBrWwQUo4c+DpTf-sdcWv+dT+rw@mail.gmail.com> (raw)
In-Reply-To: <E588AC6D-F9FF-4215-B25E-F98461D059C7@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 990 bytes --]

Sorry for the thread necromancy. What do I need to do for inclusion in GNU
ELPA?


On Thu, Jul 10, 2014 at 12:00 PM, chad <yandros@gmail.com> wrote:

> On 09 Jul 2014, at 20:59, Matt DeBoard <matt.deboard@gmail.com> wrote:
>
> > As regarding inclusion in GNU ELPA, I'm just a caretaker for the
> > project on behalf of the Elixir-lang people, but as it's already in
> > MELPA I'm sure it's fine.
>
> I would go a step further than Stefan and say that MELPA is basically the
> archetype of not-fine in this domain: finding a package in MELPA means,
> basically "someone, somewhere, wrote some code that might do something, in
> some of the versions I've had at some point". Finding a package in GNU ELPA
> (or a handful of other elpa repositories) adds things like "this version
> should actually do what's written on the tin" to potentially-interesting
> properties like "copyrights already assigned" and "can be fixed by
> interested emacs maintainers".
>
> I hope that helps,
> ~Chad
>
>

[-- Attachment #2: Type: text/html, Size: 1461 bytes --]

  reply	other threads:[~2014-08-16  2:34 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAPLdYOhnp353s3LTM9EORWbzmiH2JXVjFNX1sp07tQYe2Q4MPA@mail.gmail.com>
2014-07-10  3:02 ` SMIE Stefan Monnier
2014-07-10  3:53   ` SMIE Matt DeBoard
2014-07-10  3:59     ` SMIE Matt DeBoard
2014-07-10 17:00       ` SMIE chad
2014-08-16  2:34         ` Matt DeBoard [this message]
2014-08-17  7:27           ` SMIE Bozhidar Batsov
2014-08-17 11:55             ` SMIE Stefan Monnier
2014-08-18 12:00               ` SMIE Bozhidar Batsov
2014-08-18 13:33                 ` SMIE Tassilo Horn
2014-08-18 14:07                 ` SMIE Stefan Monnier
2014-08-19 13:08                 ` SMIE Richard Stallman
2014-08-19 14:12                   ` SMIE Bastien
2014-08-20  2:27                     ` SMIE Richard Stallman
2014-08-20  3:19                       ` SMIE Matt DeBoard
2014-08-20  3:57                         ` SMIE Ivan Andrus
2014-08-20 14:25                           ` SMIE Stefan Monnier
2014-08-27 22:44                             ` SMIE Matt DeBoard
2014-08-28  3:11                               ` SMIE Stefan Monnier
2014-08-28  7:40                                 ` SMIE David Kastrup
2014-08-28 22:03                                   ` SMIE Dmitry
2014-08-17  8:55         ` SMIE Andreas Röhler
2014-07-10 13:32     ` SMIE Stefan Monnier
2014-07-12 14:38     ` SMIE Stephen Leake
2014-07-10  4:22   ` SMIE Matt DeBoard

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='CAPLdYOhbxqXf=7YuNFSuSBARBrWwQUo4c+DpTf-sdcWv+dT+rw@mail.gmail.com' \
    --to=matt.deboard@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=yandros@gmail.com \
    /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).