all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Cc: bug-gettext@gnu.org
Subject: Re: ELPA and gettext.el
Date: Fri, 25 Jan 2019 19:53:40 -0500	[thread overview]
Message-ID: <jwvsgxgw8b2.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: 05526b27-45a5-d093-ecaf-032271c65a6e@cs.ucla.edu

> 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).

FWIW, I do pay some (limited) attention to byte-compiler warnings, and
I do occasional `grep`s which make me bump into random pieces of code
(both in emacs.git and elpa.git).  So a change in Emacs results in
sufficiently obvious breakage in po-mode, there's a chance I'd see it
and fix it.  Pretty far from a 100% chance, tho.


        Stefan




  reply	other threads:[~2019-01-26  0:53 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
2019-01-26  0:53               ` Stefan Monnier [this message]
     [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvsgxgw8b2.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=bug-gettext@gnu.org \
    --cc=emacs-devel@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.