From: Mark Mitchell <mark@codesourcery.com>
To: law@cygnus.com
Cc: gcc@gcc.gnu.org
Subject: Re: Apology
Date: Fri, 31 Dec 1999 23:54:00 -0000 [thread overview]
Message-ID: <19991229214143R.mitchell@codesourcery.com> (raw)
Message-ID: <19991231235400.0v5PXpQYP9bSw2DqeEPVmwWk-lK1otlBs-llFAJgbKY@z> (raw)
In-Reply-To: <7209.946519981@upchuck>
>>>>> "Jeffrey" == Jeffrey A Law <law@cygnus.com> writes:
Jeffrey> Mark, please accept my apology
Thank you for your very frank note.
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.
I think almost everyone on this list has at one point or another felt
short of time, irritated, etc. and that often that comes through in
our notes. I sometimes notice this when rereading my own replies to
posted C++ patches; I sometimes say "That isn't right" instead of
"Thank you for your patch. Unfortunately, ..."
Let's all look forward to the new year -- I'm sure that well work
together to make GCC an absolutely top-flight free compiler!
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
next prev parent reply other threads:[~1999-12-31 23:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-29 18:14 Apology Jeffrey A Law
1999-12-29 21:43 ` Mark Mitchell [this message]
1999-12-31 23:54 ` Apology Mark Mitchell
1999-12-31 23:54 ` Apology Jeffrey A Law
-- strict thread matches above, loose matches on Subject: below --
2001-12-06 15:14 apology Jade
1999-12-30 2:16 Apology Richard Kenner
1999-12-31 23:54 ` Apology Richard Kenner
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=19991229214143R.mitchell@codesourcery.com \
--to=mark@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=law@cygnus.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).