From: Clifford Beshers <clifford.beshers@lindows.com>
To: Reiserfs developers mail-list <Reiserfs-Dev@namesys.com>
Cc: Hans Reiser <reiser@namesys.com>,
Reiserfs mail-list <Reiserfs-List@namesys.com>
Subject: Re: mm vs. official for reiser4.
Date: Mon, 09 Feb 2004 10:05:29 -0800 [thread overview]
Message-ID: <4027CBE9.6030307@lindows.com> (raw)
In-Reply-To: <40277FF5.8050800@free.fr>
I prefer Hans' method. Limiting variables is essential for productive
testing and debugging. Get a stable FS with one kernel, make sure you
understand all the issues, then deal with forks.
Vince wrote:
> Count another vote in favour of the -mm branch. My opinion is that
> most reiser4 testers will also be likely to run the most
> "bleeding-edge" kernel branch...
>
> Hans Reiser wrote:
>
>> Until we have removed all bugs that we can hit with internal testing,
>> we will produce snapshots for use with only one kernel branch. I am
>> guessing that more reiser4 testers will use Linus kernel than
>> Morton's. Readers should correct me if I err.....
>>
>
next prev parent reply other threads:[~2004-02-09 18:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 13:26 Last reiser4 snapshot is at: http://www.namesys.com/snapshots/2004.02.06/ Nikita Danilov
2004-02-06 14:03 ` Sander
2004-02-06 14:11 ` Nikita Danilov
2004-02-06 14:30 ` Sander
2004-02-06 17:38 ` mm vs. official for reiser4 Hans Reiser
2004-02-06 4:16 ` Steven Cole
2004-02-06 17:58 ` Sander
2004-02-08 16:50 ` Craig Knox
2004-02-09 12:41 ` Vince
2004-02-09 18:05 ` Clifford Beshers [this message]
2004-02-10 0:23 ` David Masover
2004-02-07 15:22 ` stat-data problems with the 2004.02.06 snapshot Henning Westerholt
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=4027CBE9.6030307@lindows.com \
--to=clifford.beshers@lindows.com \
--cc=Reiserfs-Dev@namesys.com \
--cc=Reiserfs-List@namesys.com \
--cc=reiser@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.