From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: emacs-devel@gnu.org
Subject: Re: Bugs against emacsbugs.donarmstrong.com
Date: Wed, 17 Dec 2008 11:10:55 -0500 [thread overview]
Message-ID: <jwv1vw6ss6u.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <20081217053906.GF4782@volo.donarmstrong.com> (Don Armstrong's message of "Tue, 16 Dec 2008 21:39:06 -0800")
>> For what it's worth, I'd much rather prefer you don't touch reply-to
>> unless really necessary, so I wonder what is the reason for fiddling
>> with reply-to.
> Because a reply shouldn't go anywhere else but to the user who sent it
> and the bug itself.
You don't know that. Only the person replying knows where that reply
should go.
Besides, I don't see why getting this result requires fiddling with the
reply-to header. Can you give an example?
>> >> If "reply-to-all" sends to addresses to which the reply should
>> >> *never* be sent, then the error is not in the use of rely-to-all,
>> >> but in the headers of the email to which the user is replying.
>>
>> > No, the error is in the use of reply-to-all which include To: in
>> > addition to addresses listed in Reply-To:. The only way to work
>> > around these sorts of idiocies is to totally strip the To: header
>> > entirely, which is fundamentally broken.
>>
>> But in *no* circumstance is it right to reply to a Debbugs message
>> by sending the reply to bug-gnu-emacs or submit@bugs or
>> emacs-pretest-bug or bug-submit-list, so clearly these addresses
>> should not appear in any of the headers that might be used by "reply
>> to all".
> That would require ripping out To: from the message, and setting it to
> something entirely bogus, as I said originally.
?? I don't understand. It does mean removing those addresses from
pretty much all headers (not just To:), but I don't see why it should
require replacing it with something bogus, or why it should be
a big problem. Can you restate the problem?
Stefan
next prev parent reply other threads:[~2008-12-17 16:10 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 [this message]
2008-12-18 7:43 ` Don Armstrong
2008-12-18 21:46 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwv1vw6ss6u.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.