From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: [PATCH] Make byte-compile-error-on-warn a safe variable for file compilation
Date: Wed, 10 Jan 2018 22:22:38 +0200 [thread overview]
Message-ID: <83wp0p4g6p.fsf@gnu.org> (raw)
In-Reply-To: <CAM-tV-_yF-tYrK-DCZ1Edhv43Uez6NPM1Ck1QzX6Nz9kvzSOWg@mail.gmail.com> (message from Noam Postavsky on Wed, 10 Jan 2018 14:44:59 -0500)
> From: Noam Postavsky <npostavs@users.sourceforge.net>
> Date: Wed, 10 Jan 2018 14:44:59 -0500
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, Emacs developers <emacs-devel@gnu.org>
>
> To me, this looks like it should be considered a standard technique,
> that we shouldn't need to explain over and over again
It would be good to get there at some future point, yes.
next prev parent reply other threads:[~2018-01-10 20:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 9:40 [PATCH] Make byte-compile-error-on-warn a safe variable for file compilation Robert Cochran
2018-01-04 13:22 ` Noam Postavsky
2018-01-05 3:51 ` Stefan Monnier
2018-01-05 6:17 ` Robert Cochran
2018-01-05 12:05 ` Noam Postavsky
2018-01-06 22:42 ` Robert Cochran
2018-01-08 12:25 ` Noam Postavsky
2018-01-08 18:50 ` Eli Zaretskii
2018-01-09 3:42 ` Robert Cochran
2018-01-09 13:24 ` Stefan Monnier
2018-01-10 6:28 ` Robert Cochran
2018-01-10 15:26 ` Eli Zaretskii
2018-01-10 15:57 ` Noam Postavsky
2018-01-10 16:17 ` Eli Zaretskii
2018-01-10 16:29 ` Noam Postavsky
2018-01-10 19:36 ` Eli Zaretskii
2018-01-10 19:44 ` Noam Postavsky
2018-01-10 20:22 ` Eli Zaretskii [this message]
2018-02-12 8:21 ` Robert Cochran
2018-02-12 17:57 ` Eli Zaretskii
2018-02-13 4:49 ` Robert Cochran
[not found] ` <87tvulmrkd.fsf@cochranmail.com>
2018-02-16 15:53 ` 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=83wp0p4g6p.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=npostavs@users.sourceforge.net \
/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.