From: Chris Mason <mason@suse.com>
To: Hans Reiser <reiser@namesys.com>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org,
reiserfs-dev@namesys.com
Subject: Re: [reiserfs-dev] [PATCH] [BK] ReiserFS cleanups (third sending, but two fixes added now)
Date: 15 May 2002 10:54:31 -0400 [thread overview]
Message-ID: <1021474471.14986.700.camel@tiny> (raw)
In-Reply-To: <200205151424.g4FEOm115147@namesys.com>
On Wed, 2002-05-15 at 10:24, Hans Reiser wrote:
>
> You can pull the changes from our public server at
>
> bk://thebsh.namesys.com/bk/reiser3-linux-2.5
>
> Plain text patches are at the end of messages.
>
> Some of the changesets contain cleanups regarding labeling the code
> ownership correctly. Let me know if you want more details.
>
> 5 bugs were fixed:
>
> * journal replay from wrong device
>
> * deadlock with iput. (will duplicate patch sent separately to you by
> Mason, don't know why he sent it separately)
Because the one in the namesys tree is almost unreadable. It is
intermixed with 16 other changes (in a single changeset) then modified
by incremental fixes and merge sets. The bug fix is complex enough as
it is, the namesys version is very difficult to verify.
Please let Oleg and I work out an actual coherent group of changesets
instead of this mess.
-chris
parent reply other threads:[~2002-05-15 14:55 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200205151424.g4FEOm115147@namesys.com>]
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=1021474471.14986.700.camel@tiny \
--to=mason@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
--cc=reiserfs-dev@namesys.com \
--cc=torvalds@transmeta.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