From: Oleg Drokin <green@namesys.com>
To: Christoph Hellwig <hch@infradead.org>,
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: [reiserfs-list] Re: reiserfsprogs release
Date: Wed, 10 Jul 2002 18:47:44 +0400 [thread overview]
Message-ID: <20020710184744.A1939@namesys.com> (raw)
In-Reply-To: <20020710153801.A8570@infradead.org>
Hello!
On Wed, Jul 10, 2002 at 03:38:01PM +0100, Christoph Hellwig wrote:
> > > 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
No.
> very bad (2.4 is not supposed to need newer userlevel during the series)
Well, sometimes you want to upgrade not because it is required, but because
of bugfixed you will get out of newer version.
Bye,
Oleg
next prev parent reply other threads:[~2002-07-10 14:45 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
2002-07-10 14:46 ` Christoph Hellwig
2002-07-10 14:47 ` Oleg Drokin [this message]
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=20020710184744.A1939@namesys.com \
--to=green@namesys.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