From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: Maciej Borzecki <maciej.borzecki@rndity.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] wic: mountpoint is an optional argument
Date: Thu, 14 Jul 2016 15:28:09 +0300 [thread overview]
Message-ID: <20160714122809.GA3744@linux.intel.com> (raw)
In-Reply-To: <f797bf73d4af0da787c3bb8dd296fe03bdd16afb.1468322776.git.maciej.borzecki@rndity.com>
Hi Maciej,
Thank you for the patch! It looks good to me.
Acked-by: Ed Bartosh <ed.bartosh@linux.intel.com>
BTW, the same effect can be achieved by specifying mount point without
leading slash, i.e. part mirror --ondisk sda ....
On Tue, Jul 12, 2016 at 01:37:25PM +0200, Maciej Borzecki wrote:
> According to wic documentation partition mount point is an optional
> argument. Skipping mount point also makes sense in certain
> configurations when one needs to specify a partition that is not mounted
> by the running system, such as a recovery or a mirror partition (in dual
> rootfs setups).
>
> Signed-off-by: Maciej Borzecki <maciej.borzecki@rndity.com>
> ---
> scripts/lib/wic/ksparser.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/lib/wic/ksparser.py b/scripts/lib/wic/ksparser.py
> index 6887a7d02441165d7696318ddd132c739c8121b3..0894e2b199a299fbbed272f2e1c95e9d692e3ab1 100644
> --- a/scripts/lib/wic/ksparser.py
> +++ b/scripts/lib/wic/ksparser.py
> @@ -124,7 +124,7 @@ class KickStart():
> subparsers = parser.add_subparsers()
>
> part = subparsers.add_parser('part')
> - part.add_argument('mountpoint')
> + part.add_argument('mountpoint', nargs='?')
> part.add_argument('--active', action='store_true')
> part.add_argument('--align', type=int)
> part.add_argument("--extra-space", type=sizetype, default=10*1024)
--
Regards,
Ed
prev parent reply other threads:[~2016-07-14 12:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 11:37 [PATCH] wic: mountpoint is an optional argument Maciej Borzecki
2016-07-14 12:28 ` Ed Bartosh [this message]
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=20160714122809.GA3744@linux.intel.com \
--to=ed.bartosh@linux.intel.com \
--cc=maciej.borzecki@rndity.com \
--cc=openembedded-core@lists.openembedded.org \
/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.