From: agk@sourceware.org <agk@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2 VERSION WHATS_NEW
Date: 5 Dec 2007 22:19:24 -0000 [thread overview]
Message-ID: <20071205221924.28926.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: agk at sourceware.org 2007-12-05 22:19:24
Modified files:
. : VERSION WHATS_NEW
Log message:
pre-release
N.B. This is a big release and some regressions are inevitable.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/VERSION.diff?cvsroot=lvm2&r1=1.158&r2=1.159
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.742&r2=1.743
--- LVM2/VERSION 2007/08/24 21:05:15 1.158
+++ LVM2/VERSION 2007/12/05 22:19:24 1.159
@@ -1 +1 @@
-2.02.29-cvs (2007-08-24)
+2.02.29-cvs (2007-12-05)
--- LVM2/WHATS_NEW 2007/12/05 22:11:19 1.742
+++ LVM2/WHATS_NEW 2007/12/05 22:19:24 1.743
@@ -1,5 +1,5 @@
-Version 2.02.29 -
-==================================
+Version 2.02.29 - 5th December 2007
+===================================
Make clvmd backup vg metadata on remote nodes.
Refactor pvmove allocation code.
Decode cluster locking state in log message.
@@ -36,12 +36,12 @@
Add const attributes to pv accessor functions.
Refactor vg_add_snapshot() and lv_create_empty().
Handle new sysfs subsystem/block/devices directory structure.
- Tests are run with LVM_SYSTEM_DIR pointing to private root and /dev dirs.
+ Run test with LVM_SYSTEM_DIR pointing to private root and /dev dirs.
Fix a bug in lvm_dump.sh checks for lvm/dmsetup binaries.
Fix underquotations in lvm_dump.sh.
Refactor lvcreate stripe and mirror parameter validation.
- All tools: print --help output to stdout, not stderr.
- After a diagnostic, suggest --help, rather than printing all --help output.
+ Print --help output to stdout, not stderr.
+ After a cmdline processing error, don't print help text but suggest --help.
Add %PVS extents option to lvresize, lvextend, and lvcreate.
Add 'make check' to run tests in new subdirectory 'test'.
Moved the obsolete test subdirectory to old-tests.
next reply other threads:[~2007-12-05 22:19 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-05 22:19 agk [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-01-24 23:34 LVM2 VERSION WHATS_NEW agk
2011-01-17 16:46 agk
2010-04-19 15:24 wysochanski
2009-07-28 17:07 agk
2008-10-26 10:40 agk
2008-10-17 17:48 agk
2008-10-17 17:42 agk
2008-09-19 6:48 agk
2008-06-27 22:35 agk
2008-06-27 21:56 agk
2008-06-11 12:14 agk
2008-06-11 12:08 agk
2008-04-15 15:01 agk
2008-04-15 14:49 agk
2008-04-10 20:07 agk
2008-04-10 18:19 agk
2008-01-31 12:41 agk
2008-01-31 12:36 agk
2008-01-29 12:02 agk
2008-01-29 11:48 agk
2008-01-19 12:30 agk
2008-01-19 12:28 agk
2008-01-17 15:03 agk
2007-12-05 22:48 agk
2007-08-24 21:05 agk
2007-07-17 20:53 agk
2007-07-17 20:45 agk
2007-06-15 19:05 agk
2007-04-27 20:58 agk
2007-03-19 21:16 agk
2007-03-19 21:12 agk
2007-03-08 21:37 agk
2007-03-08 21:28 agk
2007-02-13 16:10 agk
2007-02-13 16:04 agk
2007-01-30 21:37 agk
2007-01-30 18:08 agk
2007-01-25 23:40 agk
2007-01-25 23:36 agk
2007-01-17 17:56 agk
2007-01-17 17:51 agk
2007-01-11 23:17 agk
2007-01-11 22:49 agk
2006-12-14 22:21 agk
2006-12-14 20:05 agk
2006-12-01 23:29 agk
2006-12-01 23:16 agk
2006-11-20 23:30 agk
2006-11-20 19:33 agk
2006-11-10 21:27 agk
2006-11-10 21:22 agk
2006-10-27 15:37 agk
2006-10-27 15:21 agk
2006-10-12 18:13 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=20071205221924.28926.qmail@sourceware.org \
--to=agk@sourceware.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.