"--persist" is missing the "ent" at the end.
Signed-off-by: Thomas Huth <thuth@redhat.com>
---
Sorry, I just noticed this after my previous "--undefinesource"
patch had been merged - otherwise I had sent both fixes in one
patch together...
docs/migration.html.in | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/migration.html.in b/docs/migration.html.in
index 194cf7d209..77731eeb37 100644
--- a/docs/migration.html.in
+++ b/docs/migration.html.in
@@ -253,7 +253,7 @@
migration by default. The <code>virsh</code> command has two flags to
influence this behaviour. The <code>--undefinesource</code> flag
will cause the configuration file to be removed on the source host
- after a successful migration. The <code>--persist</code> flag will
+ after a successful migration. The <code>--persistent</code> flag will
cause a configuration file to be created on the destination host
after a successful migration. The following table summarizes the
configuration file handling in all possible state and flag
@@ -272,7 +272,7 @@
<th>Source config</th>
<th>Dest config</th>
<th>--undefinesource</th>
- <th>--persist</th>
+ <th>--persistent</th>
<th>Dest type</th>
<th>Source config</th>
<th>Dest config</th>
--
2.18.4
On a Friday in 2020, Thomas Huth wrote: >"--persist" is missing the "ent" at the end. > >Signed-off-by: Thomas Huth <thuth@redhat.com> >--- > Sorry, I just noticed this after my previous "--undefinesource" > patch had been merged - otherwise I had sent both fixes in one > patch together... No need to: a) be sorry. I can't see anything helpful coming out of that feeling b) cc me - I watch libvir-list as often as my inbox c) squashing them together if they fix different issues > > docs/migration.html.in | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > >diff --git a/docs/migration.html.in b/docs/migration.html.in >index 194cf7d209..77731eeb37 100644 >--- a/docs/migration.html.in >+++ b/docs/migration.html.in >@@ -253,7 +253,7 @@ > migration by default. The <code>virsh</code> command has two flags to > influence this behaviour. The <code>--undefinesource</code> flag > will cause the configuration file to be removed on the source host >- after a successful migration. The <code>--persist</code> flag will >+ after a successful migration. The <code>--persistent</code> flag will > cause a configuration file to be created on the destination host > after a successful migration. The following table summarizes the > configuration file handling in all possible state and flag >@@ -272,7 +272,7 @@ > <th>Source config</th> > <th>Dest config</th> > <th>--undefinesource</th> >- <th>--persist</th> >+ <th>--persistent</th> > <th>Dest type</th> > <th>Source config</th> > <th>Dest config</th> Reviewed-by: Ján Tomko <jtomko@redhat.com> and pushed. Jano
© 2016 - 2024 Red Hat, Inc.