From: "Панов Андрей" <rockford@yandex.ru>
To: barebox <barebox@lists.infradead.org>
Subject: Barebox drops into shell immediately, without waiting for key (next branch)
Date: Wed, 04 Mar 2015 23:18:12 +0300 [thread overview]
Message-ID: <4994491425500292@web17m.yandex.ru> (raw)
Hello!
I've discovered that on recent next commit
"acc69bdddc50262b8f91034c248279d8dc734284 defaultenv-2: init: don't call timeout again if the user intervened"
caused barebox to enter shell without asking for pressing a key.
On Radxa Rock board. It's just me?
--
Андрей
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2015-03-04 20:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 20:18 Панов Андрей [this message]
2015-03-05 10:03 ` Sascha Hauer
2015-03-05 18:48 ` Панов Андрей
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=4994491425500292@web17m.yandex.ru \
--to=rockford@yandex.ru \
--cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox