From: Chris Mason <mason@suse.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Steven Cole <elenstev@mesatop.com>,
Vitaly Fertman <vitaly@namesys.com>,
reiserfs-list@namesys.com, linux-kernel@vger.kernel.org,
Marcelo Tosatti <marcelo@conectiva.com.br>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: reiserfsprogs release
Date: 10 Jul 2002 10:44:32 -0400 [thread overview]
Message-ID: <1026312272.5663.227.camel@tiny> (raw)
In-Reply-To: <20020710153801.A8570@infradead.org>
On Wed, 2002-07-10 at 10:38, Christoph Hellwig wrote:
> On Wed, Jul 10, 2002 at 08:23:54AM -0600, Steven Cole wrote:
> > On Wed, 2002-07-10 at 02:06, Vitaly Fertman wrote:
> > >
> > > Hi all,
> > >
> > > the latest reiserfsprogs-3.6.2 is available on our ftp site.
> > >
> >
> > Is the following patch to Documentation/Changes appropriate?
>
> Does reiserfs in 2.4.19-pre require that version? if yes it would be
> very bad (2.4 is not supposed to need newer userlevel during the series)
No, it does not require that version. It is a good idea since fsck
improves with each release though ;-)
-chris
next prev parent reply other threads:[~2002-07-10 14:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200206251829.25799.vitaly@namesys.com>
[not found] ` <20020625165254.GA30301@matrix.wg>
[not found] ` <200206261317.10813.vitaly@namesys.com>
2002-07-10 8:06 ` reiserfsprogs release Vitaly Fertman
2002-07-10 9:10 ` Brandon Low
2002-07-10 9:02 ` Vitaly Fertman
2002-07-10 14:23 ` Steven Cole
2002-07-10 14:31 ` [reiserfs-list] " Oleg Drokin
2002-07-10 14:38 ` Christoph Hellwig
2002-07-10 14:44 ` Chris Mason [this message]
2002-07-10 14:46 ` Christoph Hellwig
2002-07-10 14:47 ` [reiserfs-list] " Oleg Drokin
2002-07-11 2:27 ` Matthias Andree
2002-08-12 10:42 ` Vitaly Fertman
2002-08-12 12:09 ` Alan Cox
2002-08-12 11:00 ` Vitaly Fertman
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=1026312272.5663.227.camel@tiny \
--to=mason@suse.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=elenstev@mesatop.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=reiserfs-list@namesys.com \
--cc=vitaly@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