From: Reinhard Meyer <u-boot@emk-elektronik.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Recent changes break our update scripts, because of getenv_yesno()
Date: Fri, 31 Dec 2010 12:54:17 +0100 [thread overview]
Message-ID: <4D1DC469.1030000@emk-elektronik.de> (raw)
In-Reply-To: <20101231114252.4031A4F1@gemini.denx.de>
Dear Wolfgang Denk,
> Dear Reinhard Meyer,
>
> In message<4D1DB35A.3090105@emk-elektronik.de> you wrote:
>>
>> OK, digging deeper, the culprit actually is:
>>
>> 2010-11-28
>> Mike Frysinger
>> boot cmds: convert to getenv_yesno() with autostart
>
> There has been agreement to revert that commit.
OK, I must have missed that agreement ;)
What about adding a second parameter to getenv_yesno(), that
gives the default value when the env var does not exist?
And maybe move that function into env related source?
Best Regards,
Reinhard
next prev parent reply other threads:[~2010-12-31 11:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-31 10:33 [U-Boot] Recent changes break our update scripts, because of getenv_yesno() Reinhard Meyer
2010-12-31 10:41 ` Reinhard Meyer
2010-12-31 10:58 ` Stefano Babic
2010-12-31 11:42 ` Wolfgang Denk
2010-12-31 11:54 ` Reinhard Meyer [this message]
2010-12-31 17:59 ` Mike Frysinger
2010-12-31 10:55 ` Stefano Babic
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=4D1DC469.1030000@emk-elektronik.de \
--to=u-boot@emk-elektronik.de \
--cc=u-boot@lists.denx.de \
/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