From: Chris Mason <mason@suse.com>
To: berthiaume_wayne@emc.com
Cc: green@namesys.com, reiserfs-list@namesys.com, Mizar_Sunita@emc.com
Subject: Re: lk 2.4.19 ReiserFS Build
Date: 12 Aug 2002 12:03:26 -0400 [thread overview]
Message-ID: <1029168206.1759.664.camel@tiny> (raw)
In-Reply-To: <93F527C91A6ED411AFE10050040665D0049BFE51@corpusmx1.us.dg.com>
On Fri, 2002-08-09 at 14:16, berthiaume_wayne@emc.com wrote:
> Chris/Oleg, I'm planning to build 2.4.19-final and would like to get
> ReiserFS up to the latest stable patch level. I'm looking at the following
> but have noticed in a message from Manuel Krause that there are some Namesys
> patches he has been testing successfully.
Hi Wayne,
Sorry for the delay, things here have been a bit crazy. I've got to
head out to linux world until thursday, I should have a new barrier
patch for you then.
For the moment, I would just stick with the patches in my ftp directory.
-chris
next prev parent reply other threads:[~2002-08-12 16:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-09 18:16 lk 2.4.19 ReiserFS Build berthiaume_wayne
2002-08-12 16:03 ` Chris Mason [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-12 18:21 berthiaume_wayne
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=1029168206.1759.664.camel@tiny \
--to=mason@suse.com \
--cc=Mizar_Sunita@emc.com \
--cc=berthiaume_wayne@emc.com \
--cc=green@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 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.