public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Giacomo Catenazzi <cate@debian.org>
To: trond.myklebust@fys.uio.no
Cc: "Linux Kernel (E-mail)" <linux-kernel@vger.kernel.org>
Subject: Re: O_SYNC option doesn't work (2.4.18-3)
Date: Thu, 08 Aug 2002 09:11:24 +0200	[thread overview]
Message-ID: <3D52199C.3030408@debian.org> (raw)
In-Reply-To: fa.gkqj0av.c661ad@ifi.uio.no

Trond Myklebust wrote:
>>>>>>" " == Gregory Giguashvili <Gregoryg@ParadigmGeo.com> writes:
>>>>>
> 
>     >> You'll have to ask RedHat. 2.4.18-3 is *not* a stock Linux
>     >> kernel.
>      > What about 2.4.7-10 (Default for RH7.2)? I was referring to the
>      > latest version I have...
> 
> Same story. RedHat/Suse/... all patch their kernels with extra stuff
> that often is not included in any of Marcelo/Linus' "standard"
> kernels. The latter are found on ftp.kernel.org and mirrors...

??? You tell us that this list is only made for official kernels?
In this case it would not flood my mailing box, no -ac, no -arca/-aa,
no -dj, no..., no ide-2.4, no experimental patches... NO DEVELOPMENT!

NOO. This list is also for bug report of RH/Debian/SuSE/connectiva... kernels.
The pourpose of lkml is not only the development but also to find the
stablest kernel. The errata of RH (and other) will help Marcelo and Alan
to find the right patches to include in the official kernels.

ciao
	cate


       reply	other threads:[~2002-08-08  7:11 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.jepn5rv.uiqrqe@ifi.uio.no>
     [not found] ` <fa.gkqj0av.c661ad@ifi.uio.no>
2002-08-08  7:11   ` Giacomo Catenazzi [this message]
2002-08-08  8:06     ` O_SYNC option doesn't work (2.4.18-3) Willy Tarreau
2002-08-08 12:36       ` Alan Cox
2002-08-08 14:57 Gregory Giguashvili
2002-08-08 15:37 ` Daniel Forrest
  -- strict thread matches above, loose matches on Subject: below --
2002-08-08 13:48 Jesse Pollard
2002-08-07 20:48 Jesse Pollard
2002-08-08 10:07 ` Martin Brulisauer
2002-08-07 19:30 Gregory Giguashvili
2002-08-08 13:42 ` Trond Myklebust
2002-08-07 19:24 Gregory Giguashvili
2002-08-07 19:38 ` Trond Myklebust
2002-08-07 21:55 ` Alan Cox
2002-08-07 18:54 Gregory Giguashvili
2002-08-07 18:13 ` Trond Myklebust
2002-08-07 18:39 Gregory Giguashvili
2002-08-07 17:43 ` Trond Myklebust
2002-08-07 18:15 Jesse Pollard
2002-08-07 17:31 Gregory Giguashvili
2002-08-07 17:19 ` Trond Myklebust
2002-08-07 17:24 Gregory Giguashvili
2002-08-07 16:31 ` Trond Myklebust
2002-08-07 17:17 Gregory Giguashvili
2002-08-07 16:24 ` Trond Myklebust
2002-08-07 20:20   ` Benjamin LaHaise

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=3D52199C.3030408@debian.org \
    --to=cate@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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