From: Zdenek Kabelac <zkabelac@redhat.com>
To: lvm-devel@redhat.com
Subject: patch1/4: lvm manpages
Date: Fri, 20 Aug 2010 15:09:05 +0200 [thread overview]
Message-ID: <4C6E7E71.6020601@redhat.com> (raw)
In-Reply-To: <1282262317.3337.94.camel@fermat.scientia.net>
Dne 20.8.2010 01:58, Christoph Anton Mitterer napsal(a):
> Hi.
>
> Attached would be several patches, that (IMHO) improve the lvm(8) manpage:
>
>
>
> 1) lvm.8.empty_LV.patch
> It seems that the current "Where a list of VGs is required but is left empty, a
> list of all VGs will be substituted." is also true for LVs (checked it with
> lvdisplay, which seems to lists all LVs).
> If this is true, add the patch, to reflect this in the documentation
>
lvdisplay - with empty list will substitutes with all VGs - thus effectively
display all LVs from all VGs - but it doesn't mean there is some substitution
for LVs. It's the effect of command that it displays all LVs from given VG.
Lots of commands scans for all LVs in given VGs (i.e. vgchange).
So this patch is rejected.
Zdenek
next prev parent reply other threads:[~2010-08-20 13:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-19 23:58 patch1/4: lvm manpages Christoph Anton Mitterer
2010-08-20 13:09 ` Zdenek Kabelac [this message]
2010-08-20 13:18 ` Christoph Anton Mitterer
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=4C6E7E71.6020601@redhat.com \
--to=zkabelac@redhat.com \
--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.