From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: gmane nnir busted?
Date: Thu, 21 Jan 2016 10:24:14 +0900 [thread overview]
Message-ID: <b4m37trsp1d.fsf@jpl.org> (raw)
In-Reply-To: <m2twm798b3.fsf@boostpro.com>
On Wed, 20 Jan 2016 14:48:16 -0800, Dave Abrahams wrote:
> For example, if I go to gmane.comp.lang.swift.evolution and do `G G
> Upcoming', I get two messages back that don't even contain that word.
I got:
R. [ 1: Douglas G] [Heads up] Upcoming review of API Design Guidelines,...
R. [ 3: Ethan Dia] Re: Closure Syntax
R. [ 2: David Wai] Re: Closure Syntax
R. [ 4: Ethan Dia] Re: Closure Syntax
containing the word `upcoming'. Hmm...
GNU Emacs 25.0.50.1 (i686-pc-cygwin, GTK+ Version 3.14.13) of 2016-01-21
next prev parent reply other threads:[~2016-01-21 1:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 22:48 Dave Abrahams
2016-01-21 1:24 ` Katsumi Yamaoka [this message]
2016-01-25 6:35 ` Dave Abrahams
2016-02-06 5:48 ` Lars Ingebrigtsen
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=b4m37trsp1d.fsf@jpl.org \
--to=yamaoka@jpl.org \
--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).