unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: eggert@cs.ucla.edu, jim@meyering.net, emacs-devel@gnu.org
Subject: Re: automake's .el support vs. recent loss of byte-compile-dest-file
Date: Mon, 04 Dec 2017 05:41:42 +0200	[thread overview]
Message-ID: <83d13vyxah.fsf@gnu.org> (raw)
In-Reply-To: <uro9nfp4eu.fsf@fencepost.gnu.org> (message from Glenn Morris on Sun, 03 Dec 2017 22:18:01 -0500)

> From: Glenn Morris <rgm@gnu.org>
> Date: Sun, 03 Dec 2017 22:18:01 -0500
> Cc: eggert@cs.ucla.edu, jim@meyering.net, emacs-devel@gnu.org
> 
> Eli Zaretskii wrote:
> 
> > did you intentionally leave this deprecated feature available on
> > master?
> 
> It will be years before the default automake in some G/L distributions
> gets the relevant update.

I see, thanks.



      reply	other threads:[~2017-12-04  3:41 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
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 [this message]

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=83d13vyxah.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=jim@meyering.net \
    --cc=rgm@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).