From: Ivan Shmakov <ivan@siamics.net>
To: emacs-devel@gnu.org, ding@gnus.org
Subject: Re: news:gnu.emacs.*
Date: Thu, 30 Oct 2014 07:33:14 +0000 [thread overview]
Message-ID: <87oasu9flx.fsf@violet.siamics.net> (raw)
In-Reply-To: <v4y4rywzri.fsf@fencepost.gnu.org> (Glenn Morris's message of "Wed, 29 Oct 2014 13:29:21 -0400")
>>>>> Glenn Morris <rgm@gnu.org> writes:
>>>>> Ivan Shmakov wrote:
>> FTR, – the Message-Id:s are broken not just for news:gnu.emacs.bug
>> alone, – news:gnu.emacs.help shows exactly the same issue (see,
>> e. g., the example I've posted earlier [1]), and presumably the same
>> applies all across the gnu.emacs.* groups (or perhaps even all the
>> gnu.* ones.)
> This is a Mailman FAQ.
> http://wiki.list.org/pages/viewpage.action?pageId=4030712
ACK, thanks for the pointer.
> Nobody here at emacs-devel can do anything about the GNU newsgroups
> or mailing lists, so please don't email us about them.
The page above reads:
> If your mail program or newsreader implements message threading
> correctly (see http://www.jwz.org/doc/threading.html), then it should
> be able to deal with these differences. If not, then you should
> complain to the people responsible for implementing and supporting
> your mail program or newsreader.
I’ll be just as happy if Gnus could be made to properly handle
threading in those same newsgroups. Could we discuss possible
fixes here, please?
(I assume that Gnus is within the emacs-devel@ scope, given that
Gnus is part of GNU Emacs. Cross-posting to ding@gnus.org,
though, so feel free to drop the former on follow-up.)
--
FSF associate member #7257 http://boycottsystemd.org/ … 3013 B6A0 230E 334A
parent reply other threads:[~2014-10-30 7:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <v4y4rywzri.fsf@fencepost.gnu.org>]
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=87oasu9flx.fsf@violet.siamics.net \
--to=ivan@siamics.net \
--cc=ding@gnus.org \
--cc=emacs-devel@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.
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).