public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: Hans Reiser <reiser@namesys.com>
Cc: Oleg Drokin <green@namesys.com>,
	marcelo@conectiva.com.br, linux-kernel@vger.kernel.org,
	reiserfs-dev@namesys.com
Subject: Re: [reiserfs-dev] [BK] [2.4] Reiserfs changeset 2 out of 4, please apply.
Date: 07 May 2002 17:12:38 -0400	[thread overview]
Message-ID: <1020805958.32044.186.camel@tiny> (raw)
In-Reply-To: <3CD82859.5060707@namesys.com>

On Tue, 2002-05-07 at 15:17, Hans Reiser wrote:

> >In short, these changes are not "huge", and mostly non-intrusive.
> >
> Chris, I had much the same reaction initially, and then I looked at the 
> details, and either it fixes a real bug in a simple manner, or it is a 
> comment change, etc.  It looks bigger than it is was what I finally 
> concluded.  Perhaps there is some detail in which I am wrong, but since 
> it was all tested together I didn't feel like picking out just a few 
> lines of change to leave out (since that would actually increase the 
> risk of introducing a bug).

I think it is very important to only include critical fixes at this
stage in the release cycle, especially in a kernel where we are actively
looking for a possible bug.

I also think that patch (#3) should be integrated in 2.4.20preX, along
with the iput deadlock fix like Oleg did for 2.5.  It will clean the
code with fewer silly changes, and let us avoid rediffing the iput
deadlock fix against the new stuff.

-chris



      reply	other threads:[~2002-05-07 21:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-07 15:05 [BK] [2.4] Reiserfs changeset 2 out of 4, please apply Hans Reiser
2002-05-07 15:27 ` [reiserfs-dev] " Chris Mason
2002-05-07 15:37   ` Oleg Drokin
2002-05-07 19:17     ` Hans Reiser
2002-05-07 21:12       ` Chris Mason [this message]

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=1020805958.32044.186.camel@tiny \
    --to=mason@suse.com \
    --cc=green@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=reiser@namesys.com \
    --cc=reiserfs-dev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox