From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: <ding@gnus.org>
Subject: Re: GCC to Yahoo groups fails
Date: Fri, 4 Sep 2015 16:14:42 +0100 [thread overview]
Message-ID: <87a8t29py5.fsf@ucl.ac.uk> (raw)
In-Reply-To: <874mja452e.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Fri, 4 Sep 2015 22:44:41 +0800")
On Friday, 4 Sep 2015 at 22:44, Eric Abrahamsen wrote:
[...]
> This looks like an error we were discussing a bit earlier, related
Ah, I didn't follow the whole nnmairix discussion... :(
> And more fundamentally, I'm realizing, if an argument is noted as
> &optional, we should definitely treat it as optional!
>
> If there are no objections, I'll push that change in the morning.
This sounds the way to go. No objection from me!
Thanks,
eric
--
: Eric S Fraga, GnuPG: 0xFFFCF67D
: in Emacs 25.0.50.2 + Ma Gnus v0.14 + evil-git-ff74cfb
: BBDB version 3.1.2 (2014-04-28 23:20:47+00:00)
next prev parent reply other threads:[~2015-09-04 15:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 8:57 Eric S Fraga
2015-09-04 10:10 ` Eric S Fraga
2015-09-04 14:44 ` Eric Abrahamsen
2015-09-04 15:14 ` Eric S Fraga [this message]
2015-09-05 2:12 ` Eric Abrahamsen
2015-09-06 9:08 ` Eric S Fraga
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=87a8t29py5.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=ding@gnus.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).