From: Alasdair G Kergon <agk@redhat.com>
To: Somchai Smythe <buraphalinuxserver@gmail.com>
Cc: dm-devel@redhat.com, lvm-devel@redhat.com,
LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM release 2.02.96 / git / veritysetup
Date: Sat, 9 Jun 2012 13:28:11 +0100 [thread overview]
Message-ID: <20120609122810.GG15806@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <CAFJqGkPHjaCXPq4zYxHp_koMwxbku0w=1W0wNznM_nEnpGaUGg@mail.gmail.com>
On Sat, Jun 09, 2012 at 06:00:42PM +0700, Somchai Smythe wrote:
> Do not package LVM release 2.02.96 at all, or just the verity stuff?
Just veritysetup - its interfaces/formats are still being changed
(within userspace - no interface changes are planned on the kernel side)
and the new version will not be backwards-compatible.
Alasdair
prev parent reply other threads:[~2012-06-09 12:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-09 0:23 [linux-lvm] LVM release 2.02.96 / git / veritysetup Alasdair G Kergon
2012-06-09 8:44 ` Milan Broz
2012-06-09 11:00 ` Somchai Smythe
2012-06-09 12:28 ` Alasdair G Kergon [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=20120609122810.GG15806@agk-dp.fab.redhat.com \
--to=agk@redhat.com \
--cc=buraphalinuxserver@gmail.com \
--cc=dm-devel@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=lvm-devel@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).