From: Ricardo Martincoski <ricardo.martincoski@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/4] testing/infra/builder: dump config to log
Date: Sun, 23 Jul 2017 15:44:20 -0300 [thread overview]
Message-ID: <5974ee846d043_586e1244f2c29434@ultri3.mail> (raw)
In-Reply-To: 20170723091441.GB2917@scaer
Hello,
On Sun, Jul 23, 2017 at 06:14 AM, Yann E. MORIN wrote:
> On 2017-07-23 01:20 -0300, Ricardo Martincoski spake thusly:
[snip]
>> with open(config_file, "w+") as cf:
>> cf.write(self.config)
>> + # dump the config to the logfile for easy debugging
>> + self.logfile.write("> config:\n" + self.config)
>> + self.logfile.flush()
>
> Although the variable is named 'comfig', it is in fact a defconfig.
Good point. I will rename it (not the variable, of course) in the commit log and
in the logfile.
> Also, it is easy to miss exactly where the end of the config is, so
> maybe:
>
> - prefix all lines with 'config: ',
> or
> - add 'start config' and 'end config'.
The second one seems nicer to me, I will use '> start defconfig' and
'> end defconfig'.
>
> Otherwise;
>
> Tested-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
This is the only tag I won't keep, since I am changing this patch.
I will also account for your comment on the last patch. Thank you for the hint.
I am marking patches 2 to 4 as Changes Requested.
Patch 1 (developers file only) I will keep in patchwork as-is.
Regards,
Ricardo
next prev parent reply other threads:[~2017-07-23 18:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-23 4:20 [Buildroot] [PATCH 1/4] DEVELOPERS: add Ricardo Martincoski for support/testing Ricardo Martincoski
2017-07-23 4:20 ` [Buildroot] [PATCH 2/4] testing/infra/builder: dump config to log Ricardo Martincoski
2017-07-23 9:14 ` Yann E. MORIN
2017-07-23 18:44 ` Ricardo Martincoski [this message]
2017-07-23 21:44 ` [Buildroot] [PATCH v2 1/3] testing/infra/builder: dump defconfig " Ricardo Martincoski
2017-07-23 21:44 ` [Buildroot] [PATCH v2 2/3] support/testing: fix run-tests -j Ricardo Martincoski
2017-07-23 21:44 ` [Buildroot] [PATCH v2 3/3] testing/infra/basetest: move jlevel logic to constructor Ricardo Martincoski
2017-07-24 15:55 ` [Buildroot] [PATCH v2 1/3] testing/infra/builder: dump defconfig to log Thomas Petazzoni
2017-07-23 4:20 ` [Buildroot] [PATCH 3/4] support/testing: fix run-tests -j Ricardo Martincoski
2017-07-23 9:01 ` Yann E. MORIN
2017-07-23 4:20 ` [Buildroot] [PATCH 4/4] testing/infra/basetest: move jlevel logic to constructor Ricardo Martincoski
2017-07-23 9:20 ` Yann E. MORIN
2017-07-25 20:20 ` [Buildroot] [PATCH 1/4] DEVELOPERS: add Ricardo Martincoski for support/testing Thomas Petazzoni
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=5974ee846d043_586e1244f2c29434@ultri3.mail \
--to=ricardo.martincoski@gmail.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