From: Nick Dokos <nicholas.dokos@hp.com>
To: Ben Finney <ben+emacs@benfinney.id.au>
Cc: emacs-orgmode@gnu.org
Subject: Re: Trimming quotes
Date: Sun, 30 Dec 2012 00:01:38 -0500 [thread overview]
Message-ID: <18100.1356843698@alphaville> (raw)
In-Reply-To: Message from Ben Finney <ben+emacs@benfinney.id.au> of "Sun, 30 Dec 2012 15:30:54 +1100." <7wlicgcgap.fsf@benfinney.id.au>
Ben Finney <ben+emacs@benfinney.id.au> wrote:
> tsd@tsdye.com (Thomas S. Dye) writes:
>
> > Can you point me to trimming guidelines for digest readers?
>
> In brief: Don't respond at all to a digest message.
>
> Instead, respond to the actual message you want to respond to; that way,
> your response will include correct fields in the header to preserve the
> thread of discussion.
>
> So, treat the digest message as a one-way channel. If you think you
> might ever respond, turn off digest mode and respond to individual
> messages.
>
Tom did not respond to a digest message. He responded to an ordinary
message on the list, one that was already bloated with untrimmed
content, so the new comments in his response were a tiny fraction of the
total. That in itself is somewhat unpleasant although tolerable, but
James Harkins pointed out that for somebody reading the list in digest
form, such messages cause some hardship.
Nick
PS. FWIW, my guidelines are to trim as much as possible. I include the
question(s) that I respond to and insert my answers inline. I try to
include enough context so that somebody reading just that piece of mail
can make (at least some) sense of the questions and the answers. And I
delete any part that I'm not directly commenting on.
next prev parent reply other threads:[~2012-12-30 5:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-29 3:56 Trimming quotes James Harkins
2012-12-29 15:23 ` Thomas S. Dye
2012-12-30 1:49 ` James Harkins
2012-12-30 19:09 ` Thomas S. Dye
2012-12-31 10:12 ` Bastien
2012-12-30 4:30 ` Ben Finney
2012-12-30 5:01 ` Nick Dokos [this message]
2012-12-30 9:47 ` Ian Barton
2012-12-30 12:03 ` Ben Finney
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18100.1356843698@alphaville \
--to=nicholas.dokos@hp.com \
--cc=ben+emacs@benfinney.id.au \
--cc=emacs-orgmode@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).