public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Chris Mason <mason@suse.com>
Cc: Hans Reiser <reiser@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: Tue, 7 May 2002 19:37:19 +0400	[thread overview]
Message-ID: <20020507193719.A28170@namesys.com> (raw)
In-Reply-To: <200205071505.g47F5iE04039@namesys.com> <1020785252.32097.165.camel@tiny>

Hello!

On Tue, May 07, 2002 at 11:27:32AM -0400, Chris Mason wrote:
> >  You can get this changeset from bk://thebsh.namesys.com/bk/reiser3-linux-2.4
> >  This changeset are cleaning up reiserfscode, removes stale comments, and
> >  rewrites some "borrowed" functions so that all of the code in reiserfs subdir
> >  should now only belong to NAMESYS.
> It is the end of a release cycle on a stable kernel with huge changes to
> the IDE layer, and we have at least one unconfirmed report of problems
> with reiserfs+IDE after a crash.

That's true.

> This is not the right time to send in cleanups like this, especially
> when they bits as useless as the stuff below.  #1, #2 and #4 look like
> valid fixes.  #3 should probably be mixed with the iput deadlock fix
> like Oleg did in 2.5, and should wait until after 2.4.19.

#2 and $4 are cleanups, #1 and #3 are bugfixes.
And iput deadlock fix is too big of a change for 2.4.19, so it is not included.
Let's see how will it behave in 2.5 first.
And cleanups are harmless ones, so there is no risk of getting these in.

In short, these changes are not "huge", and mostly non-intrusive.

Bye,
    Oleg

  reply	other threads:[~2002-05-07 15:37 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 [this message]
2002-05-07 19:17     ` Hans Reiser
2002-05-07 21:12       ` Chris Mason

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=20020507193719.A28170@namesys.com \
    --to=green@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=mason@suse.com \
    --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