From: Stefan Smietanowski <stesmi@stesmi.com>
To: David Ford <david+challenge-response@blue-labs.org>
Cc: viro@parcelfarce.linux.theplanet.co.uk, root@chaos.analogic.com,
"Randy.Dunlap" <rddunlap@osdl.org>,
"Godbole,
Amarendra (GE Consumer & Industrial)" <Amarendra.Godbole@ge.com>,
linux-kernel@vger.kernel.org
Subject: Re: [OT] Re: (0 == foo), rather than (foo == 0)
Date: Wed, 10 Mar 2004 23:49:08 +0100 [thread overview]
Message-ID: <404F9B64.9030906@stesmi.com> (raw)
In-Reply-To: <404F949E.1020905@blue-labs.org>
David Ford wrote:
> I won't. I didn't say anything against inability to preserve line
> boundaries. I was, and am, referring to linear text and letting the end
> user reflow that text to suit his or her preferences.
>
> viro@parcelfarce.linux.theplanet.co.uk wrote:
>
>> Kindly piss off. My mail reading software uses vi(1) to compose the
>> reply and has enough sense to preserve the line boundaries.
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
next prev parent reply other threads:[~2004-03-10 23:01 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 [this message]
2004-03-10 23:14 ` David Ford
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=404F9B64.9030906@stesmi.com \
--to=stesmi@stesmi.com \
--cc=Amarendra.Godbole@ge.com \
--cc=david+challenge-response@blue-labs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=root@chaos.analogic.com \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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