From: isra@herraiz.org (Israel Herraiz)
Subject: [sup-talk] [PATCH] Identify list messages by list-id if list-post is not present
Date: Tue, 08 Sep 2009 14:41:51 +0200 [thread overview]
Message-ID: <1252413599-sup-7371@elly> (raw)
In-Reply-To: <1252412603-sup-9617@masanjin.net>
Excerpts from William Morgan's message of Tue Sep 08 14:25:50 +0200 2009:
> We need to figure out what the right behavior should be when replying to
> a message that you know is a list message, but where you don't know the
> list address. If there's a reliable way of extracting the list address
> from another header (From?), we can use that, but I suspect there isn't.
> If there isn't a reliable wa, then maybe the original behavior is fine
> (don't treat it specially at all).
Well, yes, after all, the broken thing here is the list, that does not
have a list-post header. So I guess that what should be fixed is that
list, not Sup :-).
I did not realize about the list address bug before sending the patch,
that's why I asked it to be merged. However, I am afraid you are
right, and I think it is worthless to implement this behavior.
Cheers,
Israel
prev parent reply other threads:[~2009-09-08 12:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-25 9:31 Israel Herraiz
2009-09-01 2:58 ` William Morgan
2009-09-01 8:51 ` Israel Herraiz
2009-09-04 13:56 ` William Morgan
2009-09-07 22:46 ` Israel Herraiz
2009-09-08 12:25 ` William Morgan
2009-09-08 12:41 ` Israel Herraiz [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=1252413599-sup-7371@elly \
--to=isra@herraiz.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