* bugtracker sets bad Mail-Followup-To
@ 2010-01-08 8:26 Sven Joachim
2010-01-08 17:26 ` Glenn Morris
0 siblings, 1 reply; 8+ messages in thread
From: Sven Joachim @ 2010-01-08 8:26 UTC (permalink / raw)
To: emacs-devel
The bugtracker sets not only Reply-To, but also Mail-Followup-To to the
submitter and nnnn@debbugs.gnu.org. It also does this when replying to
an existing report, which is very bad because it cuts off previously
CC'ed people from Reply-all followups.
Sven
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: bugtracker sets bad Mail-Followup-To
2010-01-08 8:26 bugtracker sets bad Mail-Followup-To Sven Joachim
@ 2010-01-08 17:26 ` Glenn Morris
2010-01-08 18:14 ` Drew Adams
` (2 more replies)
0 siblings, 3 replies; 8+ messages in thread
From: Glenn Morris @ 2010-01-08 17:26 UTC (permalink / raw)
To: Sven Joachim; +Cc: emacs-devel
Sven Joachim wrote:
> The bugtracker sets not only Reply-To, but also Mail-Followup-To to the
> submitter and nnnn@debbugs.gnu.org. It also does this when replying to
> an existing report, which is very bad because it cuts off previously
> CC'ed people from Reply-all followups.
It's an attempt to reduce the massive mail duplication that existed
before, when people kept replying to nnn@ and bug-gnu-emacs.
Is the right thing to do:
1) When I reply to nnn@, the mail that debbugs sends out should have
neither MFT nor RT in the headers. Then people can just followup as
normal.
2) When I send a new mail to bug-gnu-emacs or submit@, the new report
that goes out should either:
a) Have MFT set to nnn@, and no RT header (same as at present, bug
remove RT).
b) Have To: set to nnn@ rather than bug-gnu-emacs. (I think this is
preferable?)
If so, I will _try_ to implement it.
^ permalink raw reply [flat|nested] 8+ messages in thread* RE: bugtracker sets bad Mail-Followup-To
2010-01-08 17:26 ` Glenn Morris
@ 2010-01-08 18:14 ` Drew Adams
2010-01-08 18:44 ` Glenn Morris
2010-01-08 20:38 ` bugtracker sets bad Mail-Followup-To Stefan Monnier
2010-01-23 19:45 ` Glenn Morris
2 siblings, 1 reply; 8+ messages in thread
From: Drew Adams @ 2010-01-08 18:14 UTC (permalink / raw)
To: 'Glenn Morris', 'Sven Joachim'; +Cc: emacs-devel
Is this perhaps related to the fact that (at least some) bug reports sent to
emacs-pretest-bug@gnu.org never appear at bug-gnu-emacs@gnu.org?
I get an Ack message from bug-gnu-emacs@gnu.org, but the bug report itself never
gets sent on to bug-gnu-emacs@gnu.org. See thread "bug tracker down again?".
(FWIW, my mail client is Outlook 2003.)
^ permalink raw reply [flat|nested] 8+ messages in thread
* RE: bugtracker sets bad Mail-Followup-To
2010-01-08 18:14 ` Drew Adams
@ 2010-01-08 18:44 ` Glenn Morris
2010-01-08 18:55 ` Drew Adams
0 siblings, 1 reply; 8+ messages in thread
From: Glenn Morris @ 2010-01-08 18:44 UTC (permalink / raw)
To: Drew Adams; +Cc: Sven Joachim, Emacs developers
Drew Adams wrote (on Fri, 8 Jan 2010 at 10:14 -0800):
> Is this perhaps related to the fact that (at least some) bug reports
> sent to emacs-pretest-bug@gnu.org never appear at
> bug-gnu-emacs@gnu.org?
No.
> I get an Ack message from bug-gnu-emacs@gnu.org, but the bug report
> itself never gets sent on to bug-gnu-emacs@gnu.org. See thread "bug
> tracker down again?".
From past experience, I _think_ the bug-gnu-emacs mailing list
silently discards mails above a certain size.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: bugtracker sets bad Mail-Followup-To
2010-01-08 17:26 ` Glenn Morris
2010-01-08 18:14 ` Drew Adams
@ 2010-01-08 20:38 ` Stefan Monnier
2010-01-23 19:45 ` Glenn Morris
2 siblings, 0 replies; 8+ messages in thread
From: Stefan Monnier @ 2010-01-08 20:38 UTC (permalink / raw)
To: Glenn Morris; +Cc: Sven Joachim, emacs-devel
> It's an attempt to reduce the massive mail duplication that existed
> before, when people kept replying to nnn@ and bug-gnu-emacs.
> Is the right thing to do:
> 1) When I reply to nnn@, the mail that debbugs sends out should have
> neither MFT nor RT in the headers. Then people can just followup as
> normal.
> 2) When I send a new mail to bug-gnu-emacs or submit@, the new report
> that goes out should either:
> a) Have MFT set to nnn@, and no RT header (same as at present, bug
> remove RT).
> b) Have To: set to nnn@ rather than bug-gnu-emacs. (I think this is
> preferable?)
> If so, I will _try_ to implement it.
IMO, the "right" thing to do is to replace bug-gnu-emacs@gnu.org and
emacs-pretest-bug@gnu.org by nnn@debbugs.gnu.org everywhere in the
headers.
Stefan
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: bugtracker sets bad Mail-Followup-To
2010-01-08 17:26 ` Glenn Morris
2010-01-08 18:14 ` Drew Adams
2010-01-08 20:38 ` bugtracker sets bad Mail-Followup-To Stefan Monnier
@ 2010-01-23 19:45 ` Glenn Morris
2 siblings, 0 replies; 8+ messages in thread
From: Glenn Morris @ 2010-01-23 19:45 UTC (permalink / raw)
To: Stefan Monnier; +Cc: emacs-devel
Stefan Monnier wrote:
> IMO, the "right" thing to do is to replace bug-gnu-emacs@gnu.org and
> emacs-pretest-bug@gnu.org by nnn@... everywhere in the headers.
A version of this is now in place, for new reports only.
As a free bonus, X-Debbugs-CC is now handled properly (ie converted to
a real Cc in the outgoing message).
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2010-01-23 19:45 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-01-08 8:26 bugtracker sets bad Mail-Followup-To Sven Joachim
2010-01-08 17:26 ` Glenn Morris
2010-01-08 18:14 ` Drew Adams
2010-01-08 18:44 ` Glenn Morris
2010-01-08 18:55 ` Drew Adams
2010-01-08 19:19 ` bug#5325 [was RE: bugtracker sets bad Mail-Followup-To] Glenn Morris
2010-01-08 20:38 ` bugtracker sets bad Mail-Followup-To Stefan Monnier
2010-01-23 19:45 ` Glenn Morris
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).