From: "willy tarreau" <wtarreau@yahoo.fr>
To: brian@worldcontrol.com, Willy Tarreau <wtarreau@free.fr>
Cc: reddog83@chartermi.net, linux-kernel@vger.kernel.org
Subject: Re: The plethora of kernel versions
Date: Sun, 6 Jan 2002 09:53:43 +0100 (CET) [thread overview]
Message-ID: <20020106085343.70369.qmail@web20508.mail.yahoo.com> (raw)
In-Reply-To: <20020105173304.B3160@top.worldcontrol.com>
> Often there is nothing in emails that idenfity what
> versions the other is talking about.
even more true these days with 2.5. Sometimes, you can
only rely on the poster to guess what version he's
talking about. Eg: at least when I see Linus, Jens or
Dave Jones, I assume it's about 2.5 before reading the
mail.
> how about the various "versions" including something
> that I can use to identify and toss those messages I
> am not interested in.
That's what regular posters tend to do :
"[PATCH-2.4]", "[BUG in 2.2.20]", or "[OT]"...
The problem is more about newcomers who don't know
about these posting rules.
> I'm primarily a 2.4 user, why do I care about all
> this 2.5 discussion?
sometimes, a 2.5 bug/fix may also affect 2.4, and this
is only told in the message body.
Willy
___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Courrier : http://courrier.yahoo.fr
next prev parent reply other threads:[~2002-01-06 8:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-05 10:52 Linux Kernel-2.4.18-nj1 Willy Tarreau
2002-01-05 18:06 ` Tom Rini
2002-01-05 19:41 ` willy tarreau
2002-01-05 21:06 ` RFC: The Big Patch List (was: Linux Kernel-2.4.18-nj1) Matthias Andree
2002-01-05 22:13 ` John Levon
2002-01-05 21:42 ` Linux Kernel-2.4.18-nj1 Tom Rini
2002-01-06 1:33 ` The plethora of kernel versions brian
2002-01-06 8:53 ` willy tarreau [this message]
2002-01-07 11:07 Zwane Mwaikambo
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=20020106085343.70369.qmail@web20508.mail.yahoo.com \
--to=wtarreau@yahoo.fr \
--cc=brian@worldcontrol.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reddog83@chartermi.net \
--cc=wtarreau@free.fr \
/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
Powered by JetHome