From: jw schultz <jw@pegasys.ws>
To: linux-kernel@vger.kernel.org
Subject: Re: Posting format
Date: Fri, 25 Jul 2003 15:10:47 -0700 [thread overview]
Message-ID: <20030725221047.GC25838@pegasys.ws> (raw)
In-Reply-To: <200307252035.h6PKZKts001817@81-2-122-30.bradfords.org.uk>
On Fri, Jul 25, 2003 at 09:35:20PM +0100, John Bradford wrote:
> > > Can we all, please, at least do things like not repeatedly quoting the
> > > list's four-line signature, and not quoting things like .config files?
And user sigs, confidentiality declarations, etc.
> >
> > One more: don't answer to people directly, only thru the list.
> > It is quite annoying to receive the same message twice, especially if
> > on a flamewar...
> >
> > Actually I was quite surprised to learn these rules aren't
> > followed here.
>
> No, that is not the etiquette on this list, please _don't_ break the
> CC list when replying - the FAQ particularly mentions this in section
> 5.3. Breaking the CC list is very likely to reduce your chances of a
> reply from a lot of developers.
>
[snip]
>
> Receiving the same message twice is generally a non-issue - the list
> is high-volume anyway, so the odd duplicate message won't use up that
> much extra bandwidth.
And can be easily dealt with in procmail. After filing the
mailing list messages i trashcan any addressed to the lists.
Then the only time i complain is when they are sent under
seperate headers.
--
________________________________________________________________
J.W. Schultz Pegasystems Technologies
email address: jw@pegasys.ws
Remember Cernan and Schmitt
next prev parent reply other threads:[~2003-07-25 21:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-25 20:35 Posting format John Bradford
2003-07-25 22:10 ` jw schultz [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-24 18:57 John Bradford
2003-07-25 18:49 ` Leandro Guimarães Faria Corsetti Dutra
2003-07-24 17:37 Mudama, Eric
2003-07-23 20:18 2.6.0-test1-ac3 still broken on Adaptec I2O Robert L. Harris
2003-07-23 20:22 ` Christoph Hellwig
2003-07-23 22:00 ` Robert L. Harris
2003-07-23 22:53 ` Tomas Szepe
2003-07-23 23:32 ` Posting format bill davidsen
2003-07-24 0:52 ` Tomas Szepe
2003-07-24 15:14 ` Steven Cole
2003-07-24 15:47 ` Robert L. Harris
2003-07-24 16:03 ` Tomas Szepe
2003-07-24 16:52 ` Steven Cole
2003-07-24 17:15 ` Robert L. Harris
2003-07-24 17:42 ` Steven Cole
2003-07-24 16:03 ` Bas Mevissen
2003-07-24 16:05 ` Steven Cole
2003-07-24 23:15 ` Bill Davidsen
2003-07-24 23:24 ` CaT
2003-07-25 2:59 ` jw schultz
2003-07-25 3:33 ` Miles Bader
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=20030725221047.GC25838@pegasys.ws \
--to=jw@pegasys.ws \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).