From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Reply to list [was: Different key maps in different dired buffers]
Date: Fri, 27 May 2016 11:02:29 +0300 [thread overview]
Message-ID: <83mvnc0vze.fsf@gnu.org> (raw)
In-Reply-To: <20160527070959.GB27615@tuxteam.de> (tomas@tuxteam.de)
> Date: Fri, 27 May 2016 09:09:59 +0200
> From: <tomas@tuxteam.de>
> Cc: Dmitry Alexandrov <321942@gmail.com>,
> Whitfield Diffie <whitfield.diffie@gmail.com>, help-gnu-emacs@gnu.org
>
> is it (roughly) consensus here to "reply to all" instead of replying
> to list?
Either one is okay.
> I happily handle both ways, but have been scolded elsewhere for not
> (strictly) replying to list.
Don't be averted by such requirements: they are generally incorrect
(whoever subscribes to a list should be prepared to get two copies of
messages for a discussion in which they posted). Unless the list has
a written policy that everyone is required to follow, you are fine
replying to all.
next prev parent reply other threads:[~2016-05-27 8:02 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 8:14 Different key maps in different dired buffers Whitfield Diffie
2016-05-26 9:06 ` tomas
2016-05-26 12:25 ` Stefan Monnier
2016-05-26 12:37 ` tomas
2016-05-26 14:03 ` Drew Adams
2016-05-26 15:05 ` Whitfield Diffie
2016-05-26 15:24 ` Drew Adams
2016-05-26 17:46 ` Dmitry Alexandrov
2016-05-26 17:59 ` Whitfield Diffie
2016-05-26 18:05 ` Drew Adams
2016-05-27 7:09 ` Reply to list [was: Different key maps in different dired buffers] tomas
2016-05-27 8:02 ` Eli Zaretskii [this message]
2016-05-27 16:46 ` Glenn Morris
2016-05-27 18:44 ` Eli Zaretskii
2016-06-03 23:38 ` Bob Proulx
[not found] ` <mailman.787.1464997128.1216.help-gnu-emacs@gnu.org>
2016-06-04 1:40 ` Emanuel Berg
2016-06-04 2:12 ` Bob Proulx
[not found] ` <mailman.789.1465006376.1216.help-gnu-emacs@gnu.org>
2016-06-04 2:51 ` Emanuel Berg
2016-06-04 15:52 ` Dmitry Alexandrov
2016-06-04 19:41 ` Bob Proulx
2016-06-04 19:48 ` Emanuel Berg
2016-06-06 2:57 ` Bob Proulx
[not found] ` <mailman.953.1465181882.1216.help-gnu-emacs@gnu.org>
2016-06-06 3:11 ` Emanuel Berg
2016-06-04 20:05 ` Stefan Monnier
2016-06-05 10:28 ` Dmitry Alexandrov
[not found] ` <mailman.857.1465069271.1216.help-gnu-emacs@gnu.org>
2016-06-05 12:44 ` Dmitry Alexandrov
2016-06-05 13:35 ` Dmitry Alexandrov
2016-06-06 3:29 ` Bob Proulx
2016-06-08 11:43 ` Dmitry Alexandrov
2016-06-09 23:35 ` Emanuel Berg
2016-06-16 0:45 ` Bob Proulx
[not found] ` <mailman.1575.1466037955.1216.help-gnu-emacs@gnu.org>
2016-06-16 5:24 ` Emanuel Berg
[not found] ` <mailman.955.1465183780.1216.help-gnu-emacs@gnu.org>
2016-06-06 6:20 ` Emanuel Berg
2016-06-06 22:03 ` Bob Proulx
[not found] ` <mailman.1023.1465250629.1216.help-gnu-emacs@gnu.org>
2016-06-06 22:55 ` Emanuel Berg
2016-06-04 17:30 ` Bob Proulx
[not found] ` <mailman.837.1465055573.1216.help-gnu-emacs@gnu.org>
2016-06-04 18:35 ` Emanuel Berg
2016-06-05 11:00 ` Dmitry Alexandrov
[not found] ` <mailman.895.1465124454.1216.help-gnu-emacs@gnu.org>
2016-06-05 23:29 ` Emanuel Berg
[not found] ` <mailman.850.1465061448.1216.help-gnu-emacs@gnu.org>
2016-06-04 19:04 ` Emanuel Berg
2016-05-27 11:42 ` Whitfield Diffie
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=83mvnc0vze.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).