public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: Giacomo Catenazzi <cate@debian.org>
Cc: trond.myklebust@fys.uio.no,
	"Linux Kernel (E-mail)" <linux-kernel@vger.kernel.org>
Subject: Re: O_SYNC option doesn't work (2.4.18-3)
Date: Thu, 8 Aug 2002 10:06:59 +0200	[thread overview]
Message-ID: <20020808080659.GC943@alpha.home.local> (raw)
In-Reply-To: <3D52199C.3030408@debian.org>

On Thu, Aug 08, 2002 at 09:11:24AM +0200, Giacomo Catenazzi wrote:
> ??? 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!

at least, the kernel and patches you are talking about are *announced*
here, so that people have a clue about changes between versions.
 
> NOO. This list is also for bug report of RH/Debian/SuSE/connectiva... 
> kernels.

do you remember one of these vendors announcing their kernels with their
changelog here ? I think that could be a good idea anyway, because that
would tell us what set of patches they found to be stable, but unfortunately,
they don't at the moment. So nobody knows what's in without pulling regularly
their new packages from their respective sites.

> 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.

If you want to help, ask these vendors to post their errata here, associated
with the bug reports, so that anyone can benefit from it.

Cheers,
Willy


  reply	other threads:[~2002-08-08  8:03 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   ` O_SYNC option doesn't work (2.4.18-3) Giacomo Catenazzi
2002-08-08  8:06     ` Willy Tarreau [this message]
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=20020808080659.GC943@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=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