From: Oleg Drokin <green@namesys.com>
To: Francis Stevens <Francis.Stevens@bristow.co.uk>
Cc: reiserfs-list@namesys.com
Subject: Re: reiserfsprogs 3.6.7 release
Date: Fri, 2 May 2003 14:54:32 +0400 [thread overview]
Message-ID: <20030502105432.GA30025@namesys.com> (raw)
In-Reply-To: <3EB2347F.7090807@bristow.co.uk>
Hello!
On Fri, May 02, 2003 at 10:03:59AM +0100, Francis Stevens wrote:
> >>> Grab it from
> >>> ftp://ftp.namesys.com/pub/reiserfsprogs/reiserfsprogs-3.6.7.tar.gz
> >>> If you are just a user, you might want not to grab this release because
> >>> you have
> >>> rebuilt your superblock most probably. If you are representing a
> >>> distro, and
> >>> you are shipping/planning to ship reiserfsprogs-3.6.[56], you need this
> >>> release instead.
> >>Sorry if this is a dumb question, I'm currently using 3.6.3, I'm just a
> >>user should I be installing 3.6.7 ? I don't understand the bit about
> >>rebuilding the superblock.
> >Well, you might want to get 3.6.7 because of all the bugfixes since 3.6.3.
> That's what I thought, but the "you might want not to grab this release
> because..." made me wonder if there was some reason why I shouldn't.
Ah, hm. So that should in fact sound "If you already have 3.6.6 and
it works for you already, you do not need to upgrade to 3.6.7,
if you have any earlier version, it is recommended to upgrade to 3.6.7"
Does this version sounds more clear?
Bye,
Oleg
next prev parent reply other threads:[~2003-05-02 10:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-01 16:15 reiserfsprogs 3.6.7 release Oleg Drokin
2003-05-02 8:51 ` Francis Stevens
2003-05-02 8:57 ` Oleg Drokin
2003-05-02 9:03 ` Francis Stevens
2003-05-02 10:49 ` Hans Reiser
2003-05-02 10:54 ` Oleg Drokin [this message]
2003-05-02 11:09 ` Francis Stevens
2003-05-02 13:41 ` Valdis.Kletnieks
2003-05-02 13:43 ` Oleg Drokin
2003-05-02 13:53 ` Valdis.Kletnieks
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=20030502105432.GA30025@namesys.com \
--to=green@namesys.com \
--cc=Francis.Stevens@bristow.co.uk \
--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.