From: Glenn Morris <rgm@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: 18725@debbugs.gnu.org
Subject: bug#18725: [PATCH]: Emacs 24.4. Say "no" to "erase customizations?". .emacs gets written.
Date: Wed, 15 Oct 2014 12:07:37 -0400 [thread overview]
Message-ID: <orh9z52u5y.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <20141015154039.GC3093@acm.acm> (Alan Mackenzie's message of "Wed, 15 Oct 2014 15:40:39 +0000")
Alan Mackenzie wrote:
> This is going to make Glenn unhappy.
There's no "going to" about it. I'm aware that you continue to do it.
> for lack of getting a CC of my original bug report to which I could've
> replied.
I checked just now and the automated bug acknowledgment emails are still
going out, just as they always have done, and they still contain
instructions on how to reply. If you did not get one, maybe check into
your email settings.
There's also M-x gnus-read-ephemeral-emacs-bug-group, which is great.
> It seems the bug-gnu-emacs mail server has been reconfigured not to
> send CCs to people involved by default, and I'm not subscribed to
> bug-gnu-emacs at the moment.
There's been no change of configuration on bug-gnu-emacs.
People who report bugs have never been expected to be subscribed to the
list, and never will be.
I've said everything I have to say on this before.
next prev parent reply other threads:[~2014-10-15 16:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.11143.1413324683.1147.bug-gnu-emacs@gnu.org>
2014-10-14 22:04 ` bug#18725: Emacs 24.4. Say "no" to "erase customizations?". .emacs gets written Alan Mackenzie
2014-10-15 10:45 ` bug#18725: [PATCH]: " Alan Mackenzie
2014-10-15 11:37 ` Ivan Shmakov
2014-10-15 14:39 ` Stefan Monnier
2014-10-15 15:40 ` Alan Mackenzie
2014-10-15 16:07 ` Glenn Morris [this message]
2014-10-15 16:58 ` Michael Albinus
2014-10-15 18:04 ` Stefan Monnier
2014-10-15 15:52 ` Glenn Morris
2014-10-15 18:09 ` Stefan Monnier
2014-10-15 12:55 ` Alan Mackenzie
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=orh9z52u5y.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=18725@debbugs.gnu.org \
--cc=acm@muc.de \
/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).