From: Hans Reiser <reiser@namesys.com>
To: Hifumi Hisashi <hifumi.hisashi@lab.ntt.co.jp>
Cc: Chris Mason <mason@suse.com>,
reiserfs-dev@namesys.com, reiserfs-list@namesys.com,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fix problems related to journaling in Reiserfs
Date: Tue, 04 Oct 2005 03:40:04 -0700 [thread overview]
Message-ID: <43425C04.3080404@namesys.com> (raw)
In-Reply-To: <6.0.0.20.2.20051004170540.03fa4eb0@129.60.53.12>
Thanks for reviewing the code like this. Please let me know if you find
the reiser4 code to have any problems, it is very generous for you to
donate your time like this.
prev parent reply other threads:[~2005-10-04 10:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 12:39 [PATCH] fix problems related to journaling in Reiserfs Hifumi Hisashi
2005-08-31 13:42 ` michael chang
2005-09-01 0:02 ` Hifumi Hisashi
2005-09-01 0:37 ` michael chang
2005-09-01 3:30 ` Hans Reiser
2005-09-01 3:35 ` Hans Reiser
2005-09-02 2:03 ` Chris Mason
2005-10-04 8:47 ` Hifumi Hisashi
2005-10-04 10:40 ` Hans Reiser [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=43425C04.3080404@namesys.com \
--to=reiser@namesys.com \
--cc=hifumi.hisashi@lab.ntt.co.jp \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mason@suse.com \
--cc=reiserfs-dev@namesys.com \
--cc=reiserfs-list@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;
as well as URLs for NNTP newsgroup(s).