linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Joe Thornber <thornber@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Some questions about the upcoming LVM v2_02_178
Date: Wed, 13 Jun 2018 10:43:03 +0100	[thread overview]
Message-ID: <20180613094303.53zhqymzojhr5dsx@reti> (raw)
In-Reply-To: <5B207DF9020000F900022B0E@prv1-mh.provo.novell.com>

On Tue, Jun 12, 2018 at 08:14:17PM -0600, Gang He wrote:
> Hello Joe,
> 
> 
> >>> On 2018/6/12 at 22:22, in message <20180612142219.ixpzqxqws3qiwqbm@reti>, Joe
> Thornber <thornber@redhat.com> wrote:
> > On Tue, Jun 12, 2018 at 03:01:27AM -0600, Gang He wrote:
> >> Hello List,
> >> 
> >> I saw there was a tag "v2_02_178-rc1" for LVM2, then I have some questions 
> > about  the upcoming LVM v2_02_178.
> >> 1) Will there be the version v2_02_178 for LVM2? since I saw some text about 
> > Version 3.0.0 in the git change logs.
> > 
> > Yes there will be.  We've had no bug reports for the -rc, so the final
> > release will be the same as the -rc.
> Between LVM2 v2_02_178-rc1 and  LVM2 v2_02_177, 
> there will not be any components/features remove, except include some bug fixes, right?


178 dropped support for two very old metadata formats (pool and lvm1), and switched
to async io all io ops apart from logging.

  reply	other threads:[~2018-06-13  9:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-12  9:01 [linux-lvm] Some questions about the upcoming LVM v2_02_178 Gang He
2018-06-12 14:22 ` Joe Thornber
2018-06-13  2:14   ` Gang He
2018-06-13  9:43     ` Joe Thornber [this message]
2018-06-14  2:14       ` Gang He

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=20180613094303.53zhqymzojhr5dsx@reti \
    --to=thornber@redhat.com \
    --cc=linux-lvm@redhat.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;
as well as URLs for NNTP newsgroup(s).