From: "Dave Korn" <dave.korn@artimi.com>
To: "'Daniel Jacobowitz'" <drow@false.org>
Cc: "'Bob Rossi'" <bob@brasko.net>,
"'Karganov Konstantin'" <kostik@ispras.ru>,
"'GDB'" <gdb@sources.redhat.com>
Subject: RE: MI output command error
Date: Thu, 10 Mar 2005 16:48:00 -0000 [thread overview]
Message-ID: <SERRANOolmRBaYFkuut0000002c@SERRANO.CAM.ARTIMI.COM> (raw)
In-Reply-To: <20050310163329.GA15132@nevyn.them.org>
----Original Message----
>From: Daniel Jacobowitz
>Sent: 10 March 2005 16:33
> On Thu, Mar 10, 2005 at 04:22:50PM -0000, Dave Korn wrote:
>> Do you actually know what
>> the terms "asynchronous" and "synchronous" mean, or were you just kind of
>> skimming over bits that didn't make any sense to you as you read the
>> docs?
>
> Same rules apply to you as anyone else, Dave. Please make an effort to
> be polite on this list.
Sorry Bob, and all, that wasn't meant to sound quite how it came out. Let
me try and explain myself better.
It's common enough, when people are reading very technical documents and
come across technical terms that they aren't familiar with, to try and make
sense of the documentation by skipping over the unknown jargon and trying to
make sense of the rest of the context around it.
This is a reasonable strategy that works well enough often enough that
that's why people use it, but sometimes (as in the difference between
'synchronous' and 'asynchronous') it may lead people to overlook a subtle
distinction that radically changes the final meaning of the
sentence/paragraph/whatever.
So it occurred to me that maybe Bob had just skimmed over that bit,
without realising the significance of the term, and I was _trying_ just to
ask in a straightforward fashion if that was what had happened. Pardon me
for not finding a more finely-worded way of asking the question, but it
wasn't in any sense meant to be a flame. (Please note how I didn't use any
insults, swearwords, or pejoratives; it really was just a straight
question).
cheers,
DaveK
--
Can't think of a witty .sigline today....
next prev parent reply other threads:[~2005-03-10 16:48 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 2:40 Bob Rossi
2005-03-09 23:22 ` Bob Rossi
2005-03-10 9:33 ` Re[2]: " Konstantin Karganov
2005-03-10 13:06 ` Bob Rossi
2005-03-10 13:43 ` Karganov Konstantin
2005-03-10 14:01 ` Bob Rossi
2005-03-10 14:15 ` Karganov Konstantin
2005-03-10 14:40 ` Bob Rossi
2005-03-10 15:13 ` Karganov Konstantin
2005-03-10 15:52 ` Dave Korn
2005-03-10 16:09 ` 'Bob Rossi'
2005-03-10 16:13 ` Daniel Jacobowitz
2005-03-10 17:44 ` Bob Rossi
2005-03-10 17:52 ` Daniel Jacobowitz
2005-03-10 20:48 ` Bob Rossi
2005-03-10 21:10 ` Daniel Jacobowitz
2005-03-10 21:25 ` Bob Rossi
2005-03-10 16:23 ` Dave Korn
2005-03-10 16:34 ` Daniel Jacobowitz
2005-03-10 16:48 ` Dave Korn [this message]
2005-03-10 17:03 ` 'Bob Rossi'
2005-03-11 11:32 ` Re[2]: " Konstantin Karganov
2005-03-11 21:05 Nick Roberts
2005-03-11 21:31 ` Daniel Jacobowitz
2005-03-11 21:36 ` Bob Rossi
2005-03-11 21:39 ` Daniel Jacobowitz
2005-03-11 21:52 ` Nick Roberts
2005-03-12 10:23 ` Eli Zaretskii
2005-03-13 9:36 ` Nick Roberts
2005-03-13 15:40 ` Daniel Jacobowitz
2005-03-13 20:22 ` Nick Roberts
2005-03-13 20:25 ` Daniel Jacobowitz
2005-03-13 23:33 ` Nick Roberts
2005-03-13 23:38 ` Daniel Jacobowitz
2005-03-13 19:41 ` Eli Zaretskii
2005-03-14 7:16 ` Peter D HUERTER
[not found] <1110656346.18541.ezmlm@sources.redhat.com>
2005-03-14 19:11 ` Jim Ingham
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=SERRANOolmRBaYFkuut0000002c@SERRANO.CAM.ARTIMI.COM \
--to=dave.korn@artimi.com \
--cc=bob@brasko.net \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=kostik@ispras.ru \
/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