public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: mark@codesourcery.com
Cc: gcc@gcc.gnu.org
Subject: Re: Apology
Date: Thu, 30 Dec 1999 02:16:00 -0000	[thread overview]
Message-ID: <9912301025.AA18474@vlsi1.ultra.nyu.edu> (raw)

    I think that *all* of us need to remember to watch our tempers, and
    try hard, before hitting the send button, to make sure the words we
    have written convey what we mean them to convey.

The other thing we have to remember is that it's always a very risky
proposition to try to read "tone" into email since the cues that we use
to do that in normal communication aren't present and we tend to read tone
from precise word choices.  But quite often the person sending the mail
doesn't have (or isn't spending) the time to *make* those precise choices.

WARNING: multiple messages have this Message-ID
From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: mark@codesourcery.com
Cc: gcc@gcc.gnu.org
Subject: Re: Apology
Date: Fri, 31 Dec 1999 23:54:00 -0000	[thread overview]
Message-ID: <9912301025.AA18474@vlsi1.ultra.nyu.edu> (raw)
Message-ID: <19991231235400.t7pZzWe247PmQVHIY27LEW6qgl3Yg_K3DgoFPgnbvVc@z> (raw)

    I think that *all* of us need to remember to watch our tempers, and
    try hard, before hitting the send button, to make sure the words we
    have written convey what we mean them to convey.

The other thing we have to remember is that it's always a very risky
proposition to try to read "tone" into email since the cues that we use
to do that in normal communication aren't present and we tend to read tone
from precise word choices.  But quite often the person sending the mail
doesn't have (or isn't spending) the time to *make* those precise choices.

             reply	other threads:[~1999-12-30  2:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-30  2:16 Richard Kenner [this message]
1999-12-31 23:54 ` Apology Richard Kenner
  -- strict thread matches above, loose matches on Subject: below --
2001-12-06 15:14 apology Jade
1999-12-29 18:14 Apology Jeffrey A Law
1999-12-29 21:43 ` Apology Mark Mitchell
1999-12-31 23:54   ` Apology Mark Mitchell
1999-12-31 23:54 ` Apology Jeffrey A Law
1997-08-26 18:57 apology Joe Buck

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9912301025.AA18474@vlsi1.ultra.nyu.edu \
    --to=kenner@vlsi1.ultra.nyu.edu \
    --cc=gcc@gcc.gnu.org \
    --cc=mark@codesourcery.com \
    /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).