From: mbroz@sourceware.org <mbroz@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2/man dmsetup.8.in
Date: 10 Mar 2011 13:11:46 -0000 [thread overview]
Message-ID: <20110310131146.20558.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: mbroz at sourceware.org 2011-03-10 13:11:45
Modified files:
man : dmsetup.8.in
Log message:
Fix dmsetup man page typo (John Bradshaw)
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/man/dmsetup.8.in.diff?cvsroot=lvm2&r1=1.37&r2=1.38
--- LVM2/man/dmsetup.8.in 2011/02/04 19:33:54 1.37
+++ LVM2/man/dmsetup.8.in 2011/03/10 13:11:45 1.38
@@ -290,7 +290,7 @@
be removed because uninterruptible processes are waiting for
I/O to return from them, adding --force will replace the table
with one that fails all I/O, which might allow the
-process to be killed. This also runs \fBmknodes\fP afterwards.
+process to be killed. This also runs \fBmknodes\fP afterward.
.IP \fBrename
.I device_name new_name
.br
@@ -374,7 +374,7 @@
.br
Parses given cookie value and extracts any udev control flags encoded.
The output is in environment key format that is suitable for use in udev
-rules. If the flag has its symbolic name assigned then the ouput is
+rules. If the flag has its symbolic name assigned then the output is
DM_UDEV_FLAG_<flag_name>='1', DM_UDEV_FLAG<flag_position>='1' otherwise.
Subsystem udev flags don't have symbolic names assigned and these ones are
always reported as DM_SUBSYSTEM_UDEV_FLAG<flag_position>='1'. There are
next reply other threads:[~2011-03-10 13:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 13:11 mbroz [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-02-15 12:25 LVM2/man dmsetup.8.in prajnoha
2011-11-30 22:32 agk
2011-11-13 1:41 agk
2010-02-15 16:32 prajnoha
2009-11-06 1:41 agk
2009-10-22 13:12 prajnoha
2009-04-23 12:20 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=20110310131146.20558.qmail@sourceware.org \
--to=mbroz@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.