All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: reiserfs-list@namesys.com, ed@debian.org
Subject: reiserfsprogs 3.6.7 release
Date: Thu, 1 May 2003 20:15:11 +0400	[thread overview]
Message-ID: <20030501161511.GA15766@namesys.com> (raw)

Hello!

   Sigh, this is the out-of-schedule bugfix release that we release
   because reiserfsprogs-3.6.5 and reiserfsprogs-3.6.6 introduced one additional
   check that is not necessary, but breaks on old filesystems (the journal
   parameters check) and lots of users are affected.
   The only change in this release compared to 3.6.6 is changing the check
   to be only performed in case of relocated journal.

   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.

   This change was sent to some people already (namely to Ed Boraas), but it turned out
   the patch was against wrong tree and did not apply to reiserfsprogs-3.6.6 at all.

   Sorry for all the confusion.

   (And reiserfsprogs-3.6.7-pre1 is still the latest code in fact, Vitaly might release it
    as reiserfsprogs-3.6.8-pre1 after May 11th, when all these long boring russian
    holidays are over)

Bye,
    Oleg

             reply	other threads:[~2003-05-01 16:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-01 16:15 Oleg Drokin [this message]
2003-05-02  8:51 ` reiserfsprogs 3.6.7 release 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
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=20030501161511.GA15766@namesys.com \
    --to=green@namesys.com \
    --cc=ed@debian.org \
    --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.