From: Jim Meyering <jim@meyering.net>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: automake's .el support vs. recent loss of byte-compile-dest-file
Date: Wed, 22 Nov 2017 21:02:07 -0800 [thread overview]
Message-ID: <CA+8g5KFO-SQFmLk3a+yJQoBL4Cj2AY4CkMCr7pH6TRNYMmB0_A@mail.gmail.com> (raw)
In-Reply-To: <50da4282-fb9c-6de8-b054-73038a8ea338@cs.ucla.edu>
On Wed, Nov 22, 2017 at 8:56 PM, Paul Eggert <eggert@cs.ucla.edu> wrote:
> Jim Meyering wrote:
>>
>> Do you think it's worth supporting pre-23 emacs?
>
>
> Ha! We just had a thread discussing this, where I wrote:
>
>> currently I would say that Emacs 23.1 is the oldest Emacs we currently
>> need to worry about
>
> For details as to why, please see:
>
> https://lists.gnu.org/r/emacs-devel/2017-11/msg00500.html
Thanks.
Good to know the automake fix will be small.
However, bear in mind that once that May change makes it into an emacs
release, automake-generated Makefile.in files will be broken in that
respect.
next prev parent reply other threads:[~2017-11-23 5:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 4:41 automake's .el support vs. recent loss of byte-compile-dest-file Jim Meyering
2017-11-23 4:56 ` Paul Eggert
2017-11-23 5:02 ` Jim Meyering [this message]
2017-11-23 6:34 ` Eli Zaretskii
2017-11-23 16:13 ` Jim Meyering
2017-11-23 16:37 ` Eli Zaretskii
2017-11-27 1:17 ` Jim Meyering
2017-11-27 16:36 ` Eli Zaretskii
2017-11-29 3:35 ` Jim Meyering
2017-11-29 6:44 ` Paul Eggert
2017-11-29 18:23 ` Eli Zaretskii
2017-11-30 2:28 ` Jim Meyering
2017-12-02 11:32 ` Eli Zaretskii
2017-12-02 11:37 ` Eli Zaretskii
2017-12-02 11:57 ` Eli Zaretskii
2017-12-17 0:34 ` Jim Meyering
2017-12-17 15:33 ` Eli Zaretskii
2017-12-04 3:18 ` Glenn Morris
2017-12-04 3:41 ` 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=CA+8g5KFO-SQFmLk3a+yJQoBL4Cj2AY4CkMCr7pH6TRNYMmB0_A@mail.gmail.com \
--to=jim@meyering.net \
--cc=eggert@cs.ucla.edu \
--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 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).