public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Dave Jones <davej@redhat.com>,
	jmerkey@comcast.net, Pete Harlan <harlan@artselect.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Ext3 File System "Too many files" with snort
Date: Sun, 18 Jul 2004 00:22:29 -0700	[thread overview]
Message-ID: <40FA2535.4040207@namesys.com> (raw)
In-Reply-To: <4d8e3fd304071203204c51f6c4@mail.gmail.com>

Paolo Ciarrocchi wrote:

>
> I don't unserstand why
>the linux kernel release process can't be supported by a suite of test
>that has to be passed before being released a new -rc or final
>version.
>
>It seems there are now the all the tools we need but we are note using
>them to manage the releases.
>
>I'm referring to LTP, compile stats and regression test from OSDL.
>
>
>Ciao,
>               Paolo
>
>  
>
I agree with you wholeheartedly, and Namesys does in fact run FS related 
regression tests before sending its changes in. I wish others would do 
the same for their changes.

  parent reply	other threads:[~2004-07-18  7:22 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-09 19:20 Ext3 File System "Too many files" with snort jmerkey
2004-07-10  5:07 ` Hans Reiser
2004-07-10  8:33   ` Dave Jones
2004-07-10 17:37     ` Hans Reiser
2004-07-10 17:44       ` Christoph Hellwig
2004-07-10 17:57         ` Hans Reiser
2004-07-10 18:54           ` Christoph Hellwig
2004-07-10 19:23             ` Hans Reiser
2004-07-12 10:20           ` Paolo Ciarrocchi
2004-07-12 12:11             ` Jesper Juhl
2004-07-12 23:05               ` Bernd Eckenfels
2004-07-18  7:22             ` Hans Reiser [this message]
2004-07-10 19:11       ` Francois Romieu
  -- strict thread matches above, loose matches on Subject: below --
2004-07-10  6:00 jmerkey
2004-07-10  8:38 ` Dave Jones
2004-07-09 23:11 jmerkey
2004-07-09 19:01 jmerkey
2004-07-09 19:08 ` Pete Harlan
2004-07-14  3:37   ` Ben Hoskings
2004-07-09 18:51 jmerkey
2004-07-09 18:30 jmerkey
2004-07-09 18:44 ` Hans Reiser
2004-07-09 22:26 ` Andreas Dilger
2004-07-09 18:30 jmerkey
2004-07-09 16:36 jmerkey
2004-07-09 17:04 ` Dave Jones
2004-07-08 17:51 jmerkey
2004-07-08 18:21 ` Andreas Dilger
2004-07-11 14:55   ` Michelle Konzack
2004-07-11 17:16     ` Andreas Dilger

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=40FA2535.4040207@namesys.com \
    --to=reiser@namesys.com \
    --cc=davej@redhat.com \
    --cc=harlan@artselect.com \
    --cc=hch@infradead.org \
    --cc=jmerkey@comcast.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paolo.ciarrocchi@gmail.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