From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: Bugs against emacsbugs.donarmstrong.com
Date: Thu, 18 Dec 2008 16:46:57 -0500 [thread overview]
Message-ID: <jwv4p11f9gz.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <20081218074358.GN4782@volo.donarmstrong.com> (Don Armstrong's message of "Wed, 17 Dec 2008 23:43:58 -0800")
>> You don't know that.
> Of course I know where the most ordinary form of a reply should go:
> the bug, and the person sending the message.
>> Only the person replying knows where that reply should go.
> Enough people replying clearly have no clue where they should go;
> hence this entire thread.
>> Besides, I don't see why getting this result requires fiddling with
>> the reply-to header. Can you give an example?
> To: submit@bugs
> From: bar
> Subj: Bug #1234: blah
> Causes the following message to be sent to anyone who should get mail
> involving bug 1234:
> To: submit@bugs
> From: bar
> Subj: Bug #1234: blah
> Reply-To: 1234@bugs, bar
And this is wrong, because if I want to reply only to the author, most
MUAs will force me to copy&paste emails by hand, since a simply "reply
to author" will probably take the address from the "reply-to" rather
than from "From:".
So this header makes "reply to author" behave in the way appropriate for
"reply-to-all", and make "reply-to-all" misbehave (it sends both to
1234@bugs and submit@bugs, which is somewhat hacked around by Debbugs).
A good header for the email sent by Debbugs would be:
To: 1234@bugs
From: bar
Subj: Bug #1234: blah
> It'd require changing To: in the above message to some address other
> than the address the message was actually sent to, like 1234@bugs.
> Thus, a bogus value.
That's not a bogus value at all. It's The Right Thing.
What's the problem with it?
> Debbugs is basically a huge wrapper around a mailing list per bug; the
> issue we have now is that there are multiple aliases for the same
> mailing list, and neither debbugs nor emacs-bugs does message-id
> caching and /dev/null-ing, save on display of messages for debbugs.
If you got the headers right, there wouldn't be much need for such
message-id caching.
Stefan
next prev parent reply other threads:[~2008-12-18 21:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-12 12:44 Bug tracker breaks rmail-next-same-subject Eli Zaretskii
2008-12-12 19:10 ` Stefan Monnier
2008-12-12 23:16 ` Eli Zaretskii
2008-12-12 21:47 ` Don Armstrong
2008-12-12 23:03 ` Eli Zaretskii
2008-12-12 23:25 ` Don Armstrong
2008-12-12 23:36 ` Eli Zaretskii
2008-12-12 23:57 ` Don Armstrong
2008-12-13 2:41 ` Eli Zaretskii
2008-12-13 9:42 ` Don Armstrong
2008-12-13 22:58 ` Glenn Morris
2008-12-13 23:14 ` Bugs against emacsbugs.donarmstrong.com Don Armstrong
2008-12-13 23:33 ` Glenn Morris
2008-12-14 0:23 ` Don Armstrong
2008-12-14 3:51 ` Stefan Monnier
2008-12-14 8:06 ` Stephen J. Turnbull
2008-12-14 10:13 ` Don Armstrong
2008-12-14 20:53 ` Glenn Morris
2008-12-14 21:27 ` Stefan Monnier
2008-12-17 5:39 ` Don Armstrong
2008-12-17 16:10 ` Stefan Monnier
2008-12-18 7:43 ` Don Armstrong
2008-12-18 21:46 ` Stefan Monnier [this message]
2008-12-14 8:14 ` Stephen J. Turnbull
2008-12-14 2:50 ` Stefan Monnier
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwv4p11f9gz.fsf-monnier+emacsbugreports@gnu.org \
--to=monnier@iro.umontreal.ca \
--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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).