Gnus development mailing list
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: ding@gnus.org
Subject: Comments in References
Date: Wed, 24 Sep 2008 13:44:35 +0200	[thread overview]
Message-ID: <jeskrpzs2k.fsf@sykes.suse.de> (raw)

The References header can contain CFWS, but Gnus cannot cope.  For
example, when trying to fetch the parent of
<1222245299.18015.60.camel@johannes.berg> in
gmane.linux.kernel.wireless.general Gnus says it cannot fetch article
<1222242040.4183.1.camel@localhost>(sfid-20080924_094114_025986_BB83E1CF)>,
and in a thread view the message is shown as an orphan.

Should gnus-parent-id strip comments, or is this the duty of its
callers?

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."




             reply	other threads:[~2008-09-24 11:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-24 11:44 Andreas Schwab [this message]
2008-09-24 17:00 ` Reiner Steib
2008-09-24 18:49   ` Andreas Schwab
2008-09-24 20:16     ` Reiner Steib
2008-09-26  7:22       ` Bjørn Mork
2008-09-27  8:12         ` Andreas Schwab

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=jeskrpzs2k.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --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).