public inbox for lvm2-cvs@sourceware.org
help / color / mirror / Atom feed
From: snitzer@sourceware.org
To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org
Subject: LVM2 WHATS_NEW WHATS_NEW_DM
Date: Wed, 13 Jan 2010 21:48:00 -0000 [thread overview]
Message-ID: <20100113214839.11044.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: snitzer@sourceware.org 2010-01-13 21:48:39
Modified files:
. : WHATS_NEW WHATS_NEW_DM
Log message:
update WHATS_NEW and WHATS_NEW_DM to include snapshot-merge changes
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1384&r2=1.1385
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW_DM.diff?cvsroot=lvm2&r1=1.334&r2=1.335
--- LVM2/WHATS_NEW 2010/01/13 17:40:17 1.1384
+++ LVM2/WHATS_NEW 2010/01/13 21:48:39 1.1385
@@ -2,6 +2,7 @@
===================================
Fix clvmd automatic target module loading crash.
Fix allocation code not to stop at the first area of a PV that fits.
+ Add --merge to lvconvert to merge a snapshot into its origin.
Version 2.02.57 - 12th January 2010
===================================
--- LVM2/WHATS_NEW_DM 2010/01/12 14:47:00 1.334
+++ LVM2/WHATS_NEW_DM 2010/01/13 21:48:39 1.335
@@ -1,5 +1,7 @@
Version 1.02.42 -
===================================
+ Add support for the "snapshot-merge" target.
+ Introduce a third activation_proiority level in dm_tree_activate_children.
Version 1.02.41 - 12th January 2010
===================================
next reply other threads:[~2010-01-13 21:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 21:48 snitzer [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-04-29 19:05 agk
2010-07-27 21:57 agk
2010-01-15 16:18 jbrassow
2010-01-05 21:33 snitzer
2009-11-19 19:42 agk
2009-10-27 0:52 agk
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=20100113214839.11044.qmail@sourceware.org \
--to=snitzer@sourceware.org \
--cc=lvm-devel@redhat.com \
--cc=lvm2-cvs@sourceware.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).