public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ford <david+challenge-response@blue-labs.org>
To: Stefan Smietanowski <stesmi@stesmi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OT] Re: (0 == foo), rather than (foo == 0)
Date: Wed, 10 Mar 2004 18:14:11 -0500	[thread overview]
Message-ID: <404FA143.5050806@blue-labs.org> (raw)
In-Reply-To: <404F9B64.9030906@stesmi.com>

Why don't you read the whole thread.  I'm not pushing any rules, and 
I've been replying "to the top" of emails on LKML for almost ten years.  
If your mailer wraps lines wrongly, that's the fault of your mailer.  I 
haven't had problems with mixed up quoting.  Not all software is created 
inferior..  I don't have to reply if someone else has already stated 
what needed to be said.  If you don't like my quote-above-reply, then 
filter my emails.

David
p.s. If you want to follow the 'rules' of RFC 1855, then there are 
several this list is 'breaking', this RFC is informational, a guide.  
Not law.  Your message violates RFC 1855.

Stefan Smietanowski wrote:

> You also don't have a clue what replying below is all about nor do you
> respond to anything regarding quotes. How many times haven't we seen
> stupid quotes like this :
>
> > blah blah long long line ..........................
> end of last line > here is the second line that's quoted
> end of second line......... > and here starts the third one.
>
> If you haven't - lucky you. But don't try to push your
> reply-above-and-don't-give-a-piss-about-others approach.
>
> This list replies below and uses manually wrapped lines.
>
> If you want to create your own linux kernel list with other
> rules - be free to do so, but if you want to continue talking
> on this one, follow the rules on it, don't try to push your own.
>
> // Stefan


  reply	other threads:[~2004-03-10 23:16 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-10  6:16 (0 == foo), rather than (foo == 0) Godbole, Amarendra (GE Consumer & Industrial)
2004-03-10 10:34 ` Bernd Petrovitsch
2004-03-10 18:02 ` Randy.Dunlap
2004-03-10 18:33   ` Richard B. Johnson
2004-03-10 18:50     ` [OT] " David Ford
2004-03-10 19:06       ` Roland Dreier
2004-03-10 19:26         ` David Ford
2004-03-10 21:26           ` Roland Dreier
2004-03-10 22:03             ` Måns Rullgård
2004-03-11 23:12               ` Bill Davidsen
2004-03-10 19:23       ` Richard B. Johnson
2004-03-10 19:31         ` David Ford
2004-03-10 23:20           ` Frank v Waveren
2004-03-10 23:33             ` Måns Rullgård
2004-03-11  2:14             ` David Ford
2004-03-11 15:06             ` Valdis.Kletnieks
2004-03-10 23:10         ` Peter Williams
2004-03-10 21:29       ` viro
2004-03-10 22:20         ` David Ford
2004-03-10 22:42           ` Richard B. Johnson
2004-03-11  0:33             ` Micha Feigin
2004-03-11 10:47               ` Giuseppe Bilotta
2004-03-10 22:49           ` Stefan Smietanowski
2004-03-10 23:14             ` David Ford [this message]
2004-03-10 23:28               ` Måns Rullgård
2004-03-10 23:47               ` Stefan Smietanowski
2004-03-10 21:34       ` Matthew Garrett
2004-03-10 23:00     ` Peter Williams
2004-03-11  0:16       ` Randy.Dunlap
2004-03-11  2:36       ` Linus Torvalds
2004-03-11  3:08         ` Peter Williams
2004-03-11  3:19           ` Linus Torvalds
2004-03-11  4:40             ` Stefan Smietanowski
2004-03-11  9:48               ` Måns Rullgård
2004-03-11 10:29                 ` Stefan Smietanowski
2004-03-11 15:18                 ` Andreas Schwab
2004-03-11 17:42                   ` Stefan Smietanowski
2004-03-11 23:05                     ` Bill Davidsen
2004-03-11  6:50         ` Willy Tarreau
2004-03-11  7:36           ` Peter Williams
2004-03-11 15:03     ` Valdis.Kletnieks
2004-03-11 15:22       ` Richard B. Johnson
2004-03-11 15:48         ` Valdis.Kletnieks

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=404FA143.5050806@blue-labs.org \
    --to=david+challenge-response@blue-labs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stesmi@stesmi.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