From: agk@sourceware.org <agk@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2 ./WHATS_NEW man/dmsetup.8.in
Date: 9 Mar 2010 13:42:30 -0000 [thread overview]
Message-ID: <20100309134230.16301.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: agk at sourceware.org 2010-03-09 13:42:29
Modified files:
. : WHATS_NEW
man : dmsetup.8.in
Log message:
pre-release cleanups
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1457&r2=1.1458
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/man/dmsetup.8.in.diff?cvsroot=lvm2&r1=1.33&r2=1.34
--- LVM2/WHATS_NEW 2010/03/09 13:13:08 1.1457
+++ LVM2/WHATS_NEW 2010/03/09 13:42:28 1.1458
@@ -16,7 +16,7 @@
Extend core allocation code in preparation for mirrored log areas.
Rewrite clvmd init script.
Remove lvs_in_vg_activated_by_uuid_only call.
- Run device info query device by uuid only.
+ No longer fall back to looking up active devices by name if uuid not found.
Don't touch /dev in vgmknodes if activation is disabled.
Update lvm2app.h Doxygen comments and add lvm2app Doxygen config file.
Update nightly tests and lvm2app unit tests to cover tags.
--- LVM2/man/dmsetup.8.in 2010/03/08 16:05:08 1.33
+++ LVM2/man/dmsetup.8.in 2010/03/09 13:42:29 1.34
@@ -324,8 +324,8 @@
back in using the create or load commands.
With --target, only information relating to the specified target type
is displayed.
-By default encryption keys are suppressed in table output (crypt target)
-unless --showkeys parameter is supplied.
+Encryption keys are suppressed in the table output for the crypt
+target unless the --showkeys parameter is supplied.
.IP \fBtargets
.br
Displays the names and versions of the currently-loaded targets.
next reply other threads:[~2010-03-09 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 13:42 agk [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-05-27 19:00 LVM2 ./WHATS_NEW man/dmsetup.8.in snitzer
2009-09-11 16:06 prajnoha
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=20100309134230.16301.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.