From: agk@sourceware.org <agk@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2 VERSION VERSION_DM WHATS_NEW
Date: 24 Jan 2011 23:24:08 -0000 [thread overview]
Message-ID: <20110124232408.13200.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: agk at sourceware.org 2011-01-24 23:24:06
Modified files:
. : VERSION VERSION_DM WHATS_NEW
Log message:
pre-release
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/VERSION.diff?cvsroot=lvm2&r1=1.270&r2=1.271
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/VERSION_DM.diff?cvsroot=lvm2&r1=1.78&r2=1.79
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1889&r2=1.1890
--- LVM2/VERSION 2011/01/17 18:16:18 1.270
+++ LVM2/VERSION 2011/01/24 23:24:06 1.271
@@ -1 +1 @@
-2.02.82(2)-cvs (2011-01-17)
+2.02.82(2)-cvs (2011-01-24)
--- LVM2/VERSION_DM 2011/01/17 18:16:18 1.78
+++ LVM2/VERSION_DM 2011/01/24 23:24:06 1.79
@@ -1 +1 @@
-1.02.62-cvs (2011-01-17)
+1.02.62-cvs (2011-01-24)
--- LVM2/WHATS_NEW 2011/01/24 20:02:07 1.1889
+++ LVM2/WHATS_NEW 2011/01/24 23:24:06 1.1890
@@ -1,12 +1,12 @@
-Version 2.02.82 -
+Version 2.02.82 - 24th January 2011
===================================
Bring lvscan man page up-to-date.
Fix lvchange --test to exit cleanly.
Add change_tag to toollib.
Allow multiple pvchange command line options to be specified together.
+ Do not fail pvmove polling if another process cleaned up first.
+ Avoid clvmd incrementing dlm lockspace reference count more than once.
Add -f (don't fork) option to clvmd and fix clvmd -d<num> description.
- Fix possible clvmd DLM lockspace increasing reference count.
- Do not fail polling if pvmove finished in another process.
Version 2.02.81 - 17th January 2011
===================================
next reply other threads:[~2011-01-24 23:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 23:24 agk [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-01-17 18:16 LVM2 VERSION VERSION_DM WHATS_NEW 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=20110124232408.13200.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.