From: Glenn Morris <rgm@gnu.org>
To: Leo Liu <sdl.web@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Maintaining octave.el
Date: Mon, 29 Apr 2013 12:03:31 -0400 [thread overview]
Message-ID: <dihaip494c.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <m1k3nm9i7f.fsf@gmail.com> (Leo Liu's message of "Mon, 29 Apr 2013 10:36:04 +0800")
Leo Liu wrote:
> I would also like to place octave.el in ELPA so that all emacs-24 users
> can use it. Any thoughts on this? (for example how to avoid doing the
> work twice?).
Put it solely in GNU ELPA?
I doubt that was the answer you wanted, but I always saw part of the
point of GNU ELPA as moving things out of "core", not in duplicating
things.
next prev parent reply other threads:[~2013-04-29 16:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 2:36 Maintaining octave.el Leo Liu
2013-04-29 16:03 ` Glenn Morris [this message]
2013-04-29 16:29 ` Leo Liu
2013-04-30 15:59 ` Glenn Morris
2013-05-01 17:31 ` Leo Liu
2013-05-05 5:06 ` Stefan Monnier
2013-05-05 7:04 ` Leo Liu
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=dihaip494c.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=sdl.web@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).