From: Paul Eggert <eggert-764C0pRuGfqVc3sceRu5cw@public.gmane.org>
To: Bruno Haible <bruno-nWNVUoHt2MvYtjvyW6yDsg@public.gmane.org>,
Glenn Morris <rgm-mXXj517/zsQ@public.gmane.org>
Cc: emacs-devel-mXXj517/zsQ@public.gmane.org,
bug-gettext-mXXj517/zsQ@public.gmane.org
Subject: Re: ELPA and gettext.el
Date: Fri, 25 Jan 2019 12:58:23 -0800 [thread overview]
Message-ID: <05526b27-45a5-d093-ecaf-032271c65a6e@cs.ucla.edu> (raw)
In-Reply-To: <18002249.PFuSW9TAes@omega>
On 1/20/19 2:58 AM, Bruno Haible wrote:
> Would moving po-mode.el to emacs/lisp/ make it more probable that it gets
> occasional attention and maintenance from developers familiar with Emacs Lisp,
> than putting it in ELPA?
Neither would probably give it all that much attention. I don't use ELPA
so can't say much about it. Very occasionally people make system-wide
sweeps of Emacs source code to catch things, and presumably this would
include po-mode.el. However, I doubt whether there'd be much more
attention than that unless someone filed a bug report (I hope with patches).
next prev parent reply other threads:[~2019-01-25 20:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-19 1:47 ELPA and gettext.el Alexandre Garreau
[not found] ` <87zhrxxvsv.fsf-GJHrUhKTnLMAVn7cI0sOhGhLVPiuUekF@public.gmane.org>
2019-01-19 11:37 ` Bruno Haible
2019-01-19 17:58 ` [bug-gettext] " Paul Eggert
2019-01-19 22:08 ` Glenn Morris
[not found] ` <yjbm4cuwpd.fsf-iW7gFb+/I3LZHJUXO5efmti2O/JbrIOy@public.gmane.org>
2019-01-20 10:58 ` Bruno Haible
2019-01-20 18:10 ` [bug-gettext] " Alexandre Garreau
2019-01-25 20:58 ` Paul Eggert [this message]
2019-01-26 0:53 ` Stefan Monnier
[not found] ` <jwvsgxgw8b2.fsf-monnier+emacs-mXXj517/zsQ@public.gmane.org>
2019-01-26 7:18 ` Eli Zaretskii
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=05526b27-45a5-d093-ecaf-032271c65a6e@cs.ucla.edu \
--to=eggert-764c0prugfqvc3sceru5cw@public.gmane.org \
--cc=bruno-nWNVUoHt2MvYtjvyW6yDsg@public.gmane.org \
--cc=bug-gettext-mXXj517/zsQ@public.gmane.org \
--cc=emacs-devel-mXXj517/zsQ@public.gmane.org \
--cc=rgm-mXXj517/zsQ@public.gmane.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).