From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] board/pc: improve image generation
Date: Fri, 12 Oct 2018 13:04:50 +0200 [thread overview]
Message-ID: <20181012130450.64ed4b36@windsurf> (raw)
In-Reply-To: <20181011223946.cqtbipkwm2gyviiu@lois>
Hello,
(Please keep the mailing list in Cc, thanks!)
On Fri, 12 Oct 2018 00:39:46 +0200, Gr?goire Delattre wrote:
> > and then in the commit log, explain that the grub.cfg file was copied
> > to TARGET_DIR in a post-image hook, i.e after the filesystem image has
> > been generated, and that in practice it worked because the
> > board/pc/grub-bios.cfg file is the same as boot/grub2/grub.cfg, which
> > *is* copied to TARGET_DIR as part of the grub2 build process.
>
> I fixed the comment in the v2 patch.
Thanks, I had a quick look at your v2, and it looks good to me. If no
other maintainer beats me at it, I'll try to merge it tonight.
> I've changed that too.
>
> I have two questions regarding the coding style of shell scripts in buildroot in
> general:
> 1) Should we use 2/4 spaces, tab ?
Good question, we have not standardized very well our shell scripts in
general right now. Carlos Santos has started an effort to standardize
our init scripts (see series at
http://patchwork.ozlabs.org/project/buildroot/list/?series=69419), I
think we should use the same indentation.
> 2) ${MY_VAR} vs "$MY_VAR" ?
Here as well, we don't have a very strict rule. My own personal rule is
that I use $i for simple variable names, and I switch to ${foo_bar}
when the variable name becomes more complex. But again, that's just my
own personal taste. I believe Yann uses ${foo} all the time for example.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-10-12 11:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-20 14:33 [Buildroot] [PATCH 1/1] board/pc: improve image generation Grégoire Delattre
2018-10-11 19:49 ` Thomas Petazzoni
2018-10-11 22:24 ` [Buildroot] [PATCH v2 1/1] board/pc: ensure grub.cfg is copied to target filesystem Grégoire Delattre
2018-10-21 23:58 ` Matthew Weber
2018-12-31 17:48 ` Thomas Petazzoni
2019-01-23 15:19 ` Peter Korsgaard
[not found] ` <20181011223946.cqtbipkwm2gyviiu@lois>
2018-10-12 11:04 ` Thomas Petazzoni [this message]
2018-10-12 11:21 ` [Buildroot] [PATCH 1/1] board/pc: improve image generation Grégoire Delattre
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=20181012130450.64ed4b36@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