From: Alan Mackenzie <acm@muc.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: replying to Debbugs [ was: bug#18725: ]
Date: Thu, 16 Oct 2014 09:13:25 +0000 [thread overview]
Message-ID: <20141016091325.GA3421@acm.acm> (raw)
In-Reply-To: <jwvsiipyzyo.fsf-monnier+emacsbugs@gnu.org>
[ Cc: changed to emacs-devel@gnu.org ]
Hello, Stefan.
On Wed, Oct 15, 2014 at 02:04:37PM -0400, Stefan Monnier wrote:
> > This is going to make Glenn unhappy. I posted it via Usenet, for lack
> > of getting a CC of my original bug report to which I could've replied.
> IIUC by default you don't get a Cc, indeed.
> But you do receive a acknowledgment, instead, which should work fine
> for replying.
It's fine for the address, but doesn't contain the text one wants to
reply to.
> Maybe the acknowledgment should contain the original
> report as an attachment (or does it already? I can't remember and
> don't have one on hand).
> I'd expect that many users would be confused if they received an
> automatic Cc: for their bug-reports.
We get an automatic Cc: for posts to emacs-devel, and that doesn't seem
to confuse people. Well, it confused me, because I thought we did
usually get automatic Cc:'s for bug-gnu-emacs too. It seems we don't,
and haven't done for a long time.
It would seem the only practicable way to participate in bug-gnu-emacs
threads is to be subscribed to the mailing list. There seems to be no
other way (aside from NNTP posting) that one gets the addresses and the
text together.
I don't understand the bit in .../admin/notes/bugtracker that says "We
generally don't assume anyone who posts to a list is subscribed to it,
so we cc everyone on replies.", which seems to contradict the bit which
says "NB this [replying to 123@debbugs.gnu.org] only sends mail to the
bug-list, it does NOT send a CC to the original bug submitter.".
> Stefan
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2014-10-16 9:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.11143.1413324683.1147.bug-gnu-emacs@gnu.org>
[not found] ` <m1lj7g$20c9$1@colin.muc.de>
[not found] ` <jwvfvep1jsz.fsf-monnier+emacsbugs@gnu.org>
[not found] ` <20141015154039.GC3093@acm.acm>
2014-10-15 15:59 ` replying to Debbugs Ivan Shmakov
[not found] ` <87y4sh2rsj.fsf@gmx.de>
2014-10-15 17:07 ` Ivan Shmakov
2014-10-15 22:35 ` Glenn Morris
2014-10-16 2:03 ` Richard Stallman
2014-10-16 7:16 ` Glenn Morris
2014-10-16 7:34 ` Eli Zaretskii
2014-10-16 15:49 ` Glenn Morris
2014-10-16 9:21 ` Alan Mackenzie
2014-10-16 16:02 ` Glenn Morris
2014-10-16 16:43 ` James Cloos
2014-10-16 18:12 ` Richard Stallman
2014-10-29 11:12 ` news:gnu.emacs.* Ivan Shmakov
2014-10-29 17:29 ` news:gnu.emacs.* Glenn Morris
2014-10-30 7:33 ` news:gnu.emacs.* Ivan Shmakov
[not found] ` <jwvsiipyzyo.fsf-monnier+emacsbugs@gnu.org>
2014-10-16 9:13 ` Alan Mackenzie [this message]
2014-10-16 13:53 ` replying to Debbugs [ was: bug#18725: ] 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=20141016091325.GA3421@acm.acm \
--to=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).