mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: jbradford@dial.pipex.com
To: riel@conectiva.com.br (Rik van Riel)
Cc: Hell.Surfers@cwctv.net, linux-kernel@vger.kernel.org
Subject: Re: Re: OT (Re: Re: The end of embedded Linux?)
Date: Sun, 13 Oct 2002 09:40:00 +0100 (BST)	[thread overview]
Message-ID: <200210130840.g9D8e0ZL000212@darkstar.example.net> (raw)
In-Reply-To: <Pine.LNX.4.44L.0210122343580.22735-100000@imladris.surriel.com> from "Rik van Riel" at Oct 12, 2002 11:44:37 PM

> On Sat, 12 Oct 2002 Hell.Surfers@cwctv.net wrote:
> 
> > brilliantly this summerises every problem, theres no enter.. am i really
> > replying by attachment...?
> 
> Yes.  The output of your mail program is so bad that I'm
> seriously pondering killfiling all of cwctv.net, preferably
> at the SMTP level.

However bad the output of his mail program is, what is even more
irritating is the constant discussion of it on this list.

Dean, couldn't you just delete the superflous headers that it
generates when you reply?  I don't personally care about the quoting
style.

Please, everybody, read the FAQ.  This is supposed to be a technical
discussion list.  The odd funny comment, or discussion related to
kernel development is appropriate, but flamewars about Bitkeeper
licensing, or the mail application that somebody uses are not.

Please _don't_ post to the list just to get 'street cred', and make
yourself look like a 1337 k3rn37 h@x0r.  It doesn't.

For example, I take the time to mail people who send a vague bug
report to the list and don't direct it to a particular developer, to
tell them:

* Who they should address it to
* What info they should include

I _don't_ CC the list on every one of them, just so that people will
think, "Aha!  John is cool.".

John.

      reply	other threads:[~2002-10-13  8:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-12 21:23 Hell.Surfers
2002-10-13  2:44 ` Rik van Riel
2002-10-13  8:40   ` jbradford [this message]

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=200210130840.g9D8e0ZL000212@darkstar.example.net \
    --to=jbradford@dial.pipex.com \
    --cc=Hell.Surfers@cwctv.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    /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

all inboxes | Powered by JetHome®