mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vitaly Fertman <vitaly@namesys.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: reiserfs-list@namesys.com, linux-kernel@vger.kernel.org
Subject: Re: reiserfsprogs release
Date: Mon, 12 Aug 2002 15:00:23 +0400	[thread overview]
Message-ID: <200208121500.23626.vitaly@namesys.com> (raw)
In-Reply-To: <1029154185.16421.161.camel@irongate.swansea.linux.org.uk>

> On Mon, 2002-08-12 at 11:42, Vitaly Fertman wrote:
> > Hi all,
> >
> > a critical bug was fixed in reiserfsck journal replay process,
> > so we decided to release a new 3.6.3 progs with just 2 bug
> > fixes related to it.
>
> What version does reiserfsck in this report. That way I can update

All utilities have the same version as the package has, so 3.6.3.

> CHANGES to indicate the 3.6.3 bits are required.
>
> Right now it says 3.x.1b - should it now say 3.6.3 ?

This bug was introduced in 3.6.2, so 3.x.1b was not affected.
But 3.x.1b contains many other bugs which were fixed in 3.6.2.

-- 

Thanks,
Vitaly Fertman

      reply	other threads:[~2002-08-12 10:58 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     ` 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           ` [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 [this message]

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=200208121500.23626.vitaly@namesys.com \
    --to=vitaly@namesys.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®