From: "Richard L. Goerwitz III" <richard@goon.stg.brown.edu>
To: linux-sound@vger.kernel.org
Subject: Linux sound: presumptuousness (was: rplay)
Date: Thu, 17 Sep 1998 12:13:07 +0000 [thread overview]
Message-ID: <marc-linux-sound-90603603229024@msgid-missing> (raw)
> I really don't like to push, but i'm in a big hurry, so please answer
> quick! :-)
No matter how it is couched, this way of asking for help is always a breach
of etiquette in the Linux community. Nobody out here is being paid to read
this group; nobody is under any obligation to answer you at all (still less
in a hurry).
In fact, you probably will get your answer (if I had one, I'd give it to you
myself). That's the great thing about this community.
Despite the responsiveness of the Linux community, though, you should never
ever tell them to "hurry" or "answer quick", or say things like "I don't like
to push [BUT...]." It's just so unappealing and presumptuous.
Richard Goerwitz
Brown University
reply other threads:[~1998-09-17 12:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=marc-linux-sound-90603603229024@msgid-missing \
--to=richard@goon.stg.brown.edu \
--cc=linux-sound@vger.kernel.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