From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Cc: larsi+gmane@gnus.org
Subject: Re: ding article on google groups but not gmane
Date: Thu, 06 Sep 2007 12:18:32 +0900 [thread overview]
Message-ID: <b4mejhcbhx3.fsf@jpl.org> (raw)
In-Reply-To: <87fy1sjzko.fsf@jidanni.org>
>>>>> jidanni@jidanni.org wrote:
> Gentlemen, why is an article in this group,
> Message-ID: <yoijwsvfckmz.fsf@gamma02.me.chalmers.se>
> References: <87bqcsog2m.fsf@jidanni.org>
> visible on google groups, but not on gmane? Only the parent is visible
> on gmane.
> (http://news.gmane.org/group/gmane.emacs.gnus.general/last=/force_load=t)
> Good thing I checked
> http://groups.google.com/groups/search?q=\"don\'t+mark+as+read+automatically\"+gnus
> Or else I wouldn't have ever seen his valuable reply.
> The headers
> http://groups.google.com/group/gnus.ding/msg/585acf697980782b?dmode=source
> show that it went thru quimby.gnus.org.
I guess the reason is that the article <yoijwsvfckmz.fsf@...> was
first posted by the author to the gnus.ding newsgroup, and the
Gmane server has not only the gmane.emacs.gnus.general group but
also the gnus.ding group. So, the article reposted by the ding
server to the gmane.emacs.gnus.general group was rejected because
of the duplicated Message-ID (the article has already reached to
the gnus.ding group in the Gmane server before being reposted to
the gmane.emacs.gnus.general group). Similarly, it will probably
happen also when posting articles to the gmane.emacs.gnus.general
group, I guess.
prev parent reply other threads:[~2007-09-06 3:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 2:29 jidanni
2007-09-06 3:18 ` Katsumi Yamaoka [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=b4mejhcbhx3.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.org \
--cc=larsi+gmane@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).