From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] support/scripts/genimage.sh: allow setting rootpath from parameters.
Date: Mon, 6 Jan 2020 21:56:16 +0100 [thread overview]
Message-ID: <20200106215616.483b5fba@windsurf> (raw)
In-Reply-To: <20190903120951.3318-1-raphael.melotte@essensium.com>
Hello Rapha?l,
On Tue, 3 Sep 2019 14:09:51 +0200
raphael.melotte at essensium.com wrote:
> From: Rapha?l M?lotte <raphael.melotte@essensium.com>
>
> Previously the rootpath was always set to $TARGET_DIR.
> This patch allows using other directories as rootpath.
>
> When you use genimage's mountpoints to generate an image with
> multiple (non-empty) partitions, it does two things:
> - copy $TARGET_DIR to $GENIMAGE_TMP/root
> - move any mountpoint from GENIMAGE_TMP/root to $GENIMAGE_TMP/<mountpoint>
The feedback on your patch was mostly negative. In addition, in the
mean time, commit 31d1fb27b0e62a6542112a7476ff188f2f7b8d38 was made,
which ensures --rootpath points to an empty directory, solving one of
the issues pointed out by your patch.
For other use-cases, a custom call to genimage is preferred, the
support/scripts/genimage.sh is not meant to be a full-featured
replacement to calling genimage directly.
So I've marked your patch as Rejected in our patch tracking system.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2020-01-06 20:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 12:09 [Buildroot] [PATCH 1/1] support/scripts/genimage.sh: allow setting rootpath from parameters raphael.melotte at essensium.com
2019-09-18 8:42 ` Thomas Petazzoni
2019-09-22 0:55 ` Carlos Santos
2019-09-22 7:01 ` Thomas Petazzoni
2019-09-23 7:44 ` Raphaël Mélotte
2019-09-23 7:55 ` Arnout Vandecappelle
2020-01-06 20:56 ` Thomas Petazzoni [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=20200106215616.483b5fba@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox