From: Michael Sperber <sperber@deinprogramm.de>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: PATCH: Unbreak `mailcap-mailcap-entry-passes-test'
Date: Tue, 20 Oct 2015 17:55:28 +0200 [thread overview]
Message-ID: <y9leggpsff3.fsf@deinprogramm.de> (raw)
In-Reply-To: <b4mzizdy5uz.fsf@jpl.org> (Katsumi Yamaoka's message of "Tue, 20 Oct 2015 23:25:24 +0900")
I appreciate your looking at this again!
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> In the case `test' is nil, there is no `test' to be updated.
> So, the patch is harmless, but it isn't necessarily worthwhile
> except that it makes it a bit fast, I think.
You're right. Somehow I convinced myself that my mailcap entries didn't
get added. Sorry for the false alarm!
--
Regards,
Mike
prev parent reply other threads:[~2015-10-20 15:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 9:10 Michael Sperber
2015-10-20 11:11 ` Katsumi Yamaoka
2015-10-20 11:51 ` Michael Sperber
2015-10-20 14:25 ` Katsumi Yamaoka
2015-10-20 15:55 ` Michael Sperber [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=y9leggpsff3.fsf@deinprogramm.de \
--to=sperber@deinprogramm.de \
--cc=ding@gnus.org \
--cc=yamaoka@jpl.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.
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 NNTP newsgroup(s).