public inbox for lvm2-cvs@sourceware.org
help / color / mirror / Atom feed
From: agk@sourceware.org
To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org
Subject: LVM2 VERSION VERSION_DM WHATS_NEW WHATS_NEW_DM
Date: Fri, 29 Apr 2011 17:05:00 -0000 [thread overview]
Message-ID: <20110429170521.16241.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: agk@sourceware.org 2011-04-29 17:05:21
Modified files:
. : VERSION VERSION_DM WHATS_NEW WHATS_NEW_DM
Log message:
post-release
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/VERSION.diff?cvsroot=lvm2&r1=1.277&r2=1.278
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/VERSION_DM.diff?cvsroot=lvm2&r1=1.84&r2=1.85
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1978&r2=1.1979
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW_DM.diff?cvsroot=lvm2&r1=1.464&r2=1.465
--- LVM2/VERSION 2011/04/29 16:12:21 1.277
+++ LVM2/VERSION 2011/04/29 17:05:20 1.278
@@ -1 +1 @@
-2.02.85(2)-cvs (2011-04-29)
+2.02.86(2)-cvs (2011-04-29)
--- LVM2/VERSION_DM 2011/04/29 16:12:21 1.84
+++ LVM2/VERSION_DM 2011/04/29 17:05:20 1.85
@@ -1 +1 @@
-1.02.64-cvs (2011-04-29)
+1.02.65-cvs (2011-04-29)
--- LVM2/WHATS_NEW 2011/04/29 16:27:09 1.1978
+++ LVM2/WHATS_NEW 2011/04/29 17:05:20 1.1979
@@ -1,3 +1,6 @@
+Version 2.02.86 -
+=================================
+
Version 2.02.85 - 29th April 2011
=================================
Add new obtain_device_list_from_udev setting to lvm.conf.
--- LVM2/WHATS_NEW_DM 2011/04/29 16:12:21 1.464
+++ LVM2/WHATS_NEW_DM 2011/04/29 17:05:20 1.465
@@ -1,3 +1,6 @@
+Version 1.02.65 -
+==================================
+
Version 1.02.64 - 29th April 2011
==================================
Require libudev >= 143 when compiling with udev support.
next reply other threads:[~2011-04-29 17:05 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 17:05 agk [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-06 4:47 agk
2012-03-03 2:08 agk
2012-03-03 1:00 agk
2012-02-23 18:22 agk
2012-01-27 1:23 agk
2011-08-19 19:42 agk
2011-08-19 16:31 agk
2011-08-12 2:34 agk
2011-08-12 1:34 agk
2011-07-08 19:57 agk
2011-07-08 19:19 agk
2011-04-29 16:12 agk
2011-02-09 12:11 agk
2011-02-09 12:04 agk
2011-02-04 22:46 agk
2011-01-10 14:51 agk
2010-12-21 1:08 agk
2010-12-06 22:13 agk
2010-11-22 18:38 agk
2010-11-22 14:26 agk
2010-09-24 16:25 agk
2010-08-19 22:33 agk
2010-08-18 20:57 agk
2010-07-28 21:58 agk
2010-07-28 11:49 agk
2010-07-27 22:52 agk
2010-07-06 16:49 agk
2010-06-30 14:50 agk
2010-06-23 19:35 agk
2010-06-23 17:48 agk
2010-06-07 10:25 agk
2010-06-04 17:23 agk
2010-05-20 23:21 agk
2010-05-20 22:27 agk
2010-05-17 20:18 agk
2010-04-30 15:48 agk
2010-04-14 21:47 agk
2010-04-14 17:50 agk
2010-03-09 14:01 agk
2010-03-09 13:13 agk
2010-01-23 2:14 agk
2010-01-22 1:09 agk
2010-01-21 23:55 agk
2010-01-14 14:42 agk
2010-01-14 14:02 agk
2010-01-12 14:47 agk
2010-01-12 14:39 agk
2009-11-24 19:04 agk
2009-11-24 18:26 agk
2009-11-19 19:53 agk
2009-11-19 19:00 agk
2009-10-27 1:13 agk
2009-10-26 21:56 agk
2009-09-26 0:42 agk
2009-09-25 18:32 agk
2009-09-15 13:54 agk
2009-09-15 10:57 agk
2009-08-06 19:32 agk
2009-07-28 20:47 agk
2009-07-15 15:38 agk
2009-07-15 13:20 agk
2009-07-01 9:31 agk
2009-06-30 18:41 agk
2009-06-26 10:57 agk
2009-05-22 15:23 agk
2009-03-03 18:25 agk
2009-03-03 13:03 agk
2009-01-26 14:46 agk
2009-01-26 13:14 agk
2008-11-19 14:14 agk
2008-11-10 12:39 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=20110429170521.16241.qmail@sourceware.org \
--to=agk@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).