From: Gang He <GHe@suse.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Which lvm2 code branches are important?
Date: Thu, 11 Jul 2019 02:25:59 +0000 [thread overview]
Message-ID: <CH2PR18MB32067BD6FBA17E47168C2597CFF30@CH2PR18MB3206.namprd18.prod.outlook.com> (raw)
In-Reply-To: <c6f91be7-fc45-3233-315d-70e1bc8eb9cc@redhat.com>
Hello Marian,
Thank for your reply.
About the detailed changes for V2.03, where do we can find the related documents from the external link?
Thanks
Gang
-----Original Message-----
From: linux-lvm-bounces@redhat.com [mailto:linux-lvm-bounces@redhat.com] On Behalf Of Marian Csontos
Sent: 2019��7��10�� 20:48
To: LVM general discussion and development <linux-lvm@redhat.com>; Gang He <GHe@suse.com>
Subject: Re: [linux-lvm] Which lvm2 code branches are important?
On 7/10/19 8:42 AM, Gang He wrote:
> Hello List,
>
> After you clone the code from git://sourceware.org/git/lvm2.git, you can find lots of remote code branches.
> But which code branches are important for the third party users/ developer? That means we should monitor these code branches.
> For example,
> Which code branches are main (or long-active) code branches?
> Which code branches are used for which lvm2 products (big versions)?
master - 2.03 branch, new features land here,
stable-2.02 - legacy 2.02 branch, bug fixes mostly.
> What are the main differences between different lvm2 products? E.g. some features are added/removed.
2.03 vs 2.03:
- dropped lvmetad and clvmd,
- added handling of writecache and VDO targets.
>
>
> Thanks a lot.
> Gang
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
next prev parent reply other threads:[~2019-07-11 2:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 6:42 [linux-lvm] Which lvm2 code branches are important? Gang He
2019-07-10 12:47 ` Marian Csontos
2019-07-11 2:25 ` Gang He [this message]
2019-07-24 13:43 ` Marian Csontos
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=CH2PR18MB32067BD6FBA17E47168C2597CFF30@CH2PR18MB3206.namprd18.prod.outlook.com \
--to=ghe@suse.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).