All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Teigland <teigland@sourceware.org>
To: lvm-devel@redhat.com
Subject: master - man: vgsplit source and destination VGs
Date: Tue, 17 Nov 2020 17:02:23 +0000 (GMT)	[thread overview]
Message-ID: <20201117170223.9AA763896807@sourceware.org> (raw)

Gitweb:        https://sourceware.org/git/?p=lvm2.git;a=commitdiff;h=9c0253d930103c33784fac5b303da20104a314b6
Commit:        9c0253d930103c33784fac5b303da20104a314b6
Parent:        aba9652e584b6f6a422233dea951eb59326a3de2
Author:        David Teigland <teigland@redhat.com>
AuthorDate:    Tue Nov 17 11:00:40 2020 -0600
Committer:     David Teigland <teigland@redhat.com>
CommitterDate: Tue Nov 17 11:00:40 2020 -0600

man: vgsplit source and destination VGs

make clearer which is source and which is destination
---
 man/vgsplit.8_des | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/man/vgsplit.8_des b/man/vgsplit.8_des
index 29eb5c5cb..d42ff1628 100644
--- a/man/vgsplit.8_des
+++ b/man/vgsplit.8_des
@@ -1,6 +1,7 @@
-vgsplit moves one or more PVs from a source VG to a destination VG. The
-PVs can be specified explicitly or implicitly by naming an LV, in which
-case on PVs underlying the LV are moved.
+vgsplit moves one or more PVs from a source VG (the first VG arg) to a
+destination VG (the second VG arg).  The PV(s) to move are named after the
+source and destination VGs, or an LV is named, in which case the PVs
+underlying the LV are moved.
 
 If the destination VG does not exist, a new VG is created (command options
 can be used to specify properties of the new VG, also see



                 reply	other threads:[~2020-11-17 17:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20201117170223.9AA763896807@sourceware.org \
    --to=teigland@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.