From: Alex Branham <alex.branham@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 34290-done@debbugs.gnu.org
Subject: bug#34290: [PATCH] checkdoc byte compile warnings
Date: Fri, 08 Feb 2019 16:27:57 -0600 [thread overview]
Message-ID: <87pns1oqz6.fsf@gmail.com> (raw)
In-Reply-To: <83ftt6w3lc.fsf@gnu.org>
On Sat 02 Feb 2019 at 10:35, Eli Zaretskii <eliz@gnu.org> wrote:
> Thanks, this looks good. Let's wait for a few days for additional
> comments, if someone would like to voice them.
Pushed as 1e155dcc8dcbaed926a1574bc543d404d2859866
prev parent reply other threads:[~2019-02-08 22:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-02 15:47 bug#34290: [PATCH] checkdoc byte compile warnings Alex Branham
2019-02-02 16:06 ` Eli Zaretskii
2019-02-02 16:28 ` Alex Branham
2019-02-02 16:35 ` Eli Zaretskii
2019-02-08 22:27 ` Alex Branham [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=87pns1oqz6.fsf@gmail.com \
--to=alex.branham@gmail.com \
--cc=34290-done@debbugs.gnu.org \
--cc=eliz@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).