From: Chong Yidong <cyd@stupidchicken.com>
To: rms@gnu.org
Cc: bzg@altern.org, emacs-devel@gnu.org, monnier@iro.umontreal.ca,
kjambunathan@gmail.com
Subject: Re: [ELPA Submission] OpenDocumentText exporter for Orgmode
Date: Sat, 09 Jul 2011 14:31:50 -0400 [thread overview]
Message-ID: <8762nbxq3t.fsf@stupidchicken.com> (raw)
In-Reply-To: <E1QfYfG-0003aV-S0@fencepost.gnu.org> (Richard Stallman's message of "Sat, 09 Jul 2011 10:37:50 -0400")
Richard Stallman <rms@gnu.org> writes:
> > He meant GNU ELPA but he said the name of Tom's archive. You could
> > tell from the context which one he meant, but if you need to tell from
> > the context, that is proof that the names are not clear.
>
> All the other alternatives are lousy; that's life.
>
> Several good alternatives have been suggested here,
> including REL and REEL.
>
> Do you have any objective reasons to reject them?
As I explained in a previous email, "Emacs Lisp Package Archive" is the
natural name to use when referring to archives compatible with
package.el, which internally refers to `packages' and `archives' in its
many functions, variables, and documentation; nor is it reasonable to
rename all these functions and variables, because it is good to maintain
compatibility with existing users of Tom's original package.el.
Given that ELPA is the natural term for archives compatible with
package.el, it does not make sense for us to name our archive something
completely different---and less descriptive.
next prev parent reply other threads:[~2011-07-09 18:31 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 20:25 [ELPA Submission] OpenDocumentText exporter for Orgmode Jambunathan K
2011-06-14 15:50 ` Chong Yidong
2011-06-14 20:05 ` Jambunathan K
2011-06-14 21:09 ` Jambunathan K
2011-06-18 3:15 ` Stefan Monnier
2011-06-18 5:22 ` Jambunathan K
2011-06-18 16:11 ` Chong Yidong
2011-06-18 19:55 ` Stefan Monnier
2011-06-25 22:38 ` Jambunathan K
2011-07-01 18:09 ` Jambunathan K
2011-07-04 15:52 ` Stefan Monnier
2011-07-05 10:11 ` Bastien
2011-07-05 21:05 ` Richard Stallman
2011-07-08 9:52 ` Bastien
2011-07-08 18:31 ` Richard Stallman
2011-07-08 18:38 ` Bastien
2011-07-08 18:59 ` Stefan Monnier
2011-07-09 1:02 ` Richard Stallman
2011-07-09 2:41 ` Chong Yidong
2011-07-09 14:37 ` Richard Stallman
2011-07-09 18:31 ` Chong Yidong [this message]
2011-07-10 0:40 ` Richard Stallman
2011-07-11 4:18 ` Stefan Monnier
2011-07-11 15:19 ` Richard Stallman
2011-07-09 19:57 ` PJ Weisberg
2011-07-09 3:05 ` Jambunathan K
2011-07-09 14:37 ` Richard Stallman
2011-06-19 14:06 ` [PATCH] OpenDocument schema files Jambunathan K
2011-06-19 14:19 ` Jambunathan K
2011-06-19 16:23 ` Eli Zaretskii
2011-06-19 18:53 ` Jambunathan K
2011-07-12 12:27 ` Jambunathan K
2011-07-12 14:54 ` Bastien
2011-06-19 16:23 ` Eli Zaretskii
2011-06-24 16:01 ` [ELPA Submission] OpenDocumentText exporter for Orgmode Bastien
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=8762nbxq3t.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=bzg@altern.org \
--cc=emacs-devel@gnu.org \
--cc=kjambunathan@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=rms@gnu.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).