From: "Jan Lübbe" <jlu@pengutronix.de>
To: barebox@lists.infradead.org
Subject: Re: envfs: provide an intentional way to ignore an existing external environment
Date: Wed, 30 Jul 2014 17:28:13 +0200 [thread overview]
Message-ID: <1406734093.22823.134.camel@coredoba.hi.pengutronix.de> (raw)
In-Reply-To: <1406715606-6821-1-git-send-email-jbe@pengutronix.de>
Hi Jürgen!
This looks good so far.
On Wed, 2014-07-30 at 12:20 +0200, Juergen Borleis wrote:
> This change set adds a new option to the saveenv command which will
> write an empty environment without content. But it will be marked as a
> placeholder and thus should be "ignored" and barebox falls back to its
> built-in default environment.
I haven't found where the environment loading is changed to implement
this behavior. Is a patch missing?
Thanks,
Jan
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-07-30 15:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 10:20 Juergen Borleis
2014-07-30 10:20 ` [PATCH 1/3] " Juergen Borleis
2014-07-30 10:20 ` [PATCH 2/3] saveenv: change API to be able to forward special flags into the envfs superblock Juergen Borleis
2014-07-30 10:20 ` [PATCH 3/3] saveenv: provide a zeroed/empty/ignore environment Juergen Borleis
2014-07-30 15:28 ` Jan Lübbe [this message]
2014-07-30 21:09 ` envfs: provide an intentional way to ignore an existing external environment Sascha Hauer
2014-07-31 7:14 ` Uwe Kleine-König
2014-07-31 7:33 ` Juergen Borleis
2014-07-31 7:44 ` Uwe Kleine-König
2014-07-31 8:03 ` Juergen Borleis
2014-08-06 3:56 ` Jean-Christophe PLAGNIOL-VILLARD
2014-08-06 7:04 ` Michael Olbrich
2014-08-06 7:28 ` Uwe Kleine-König
2014-08-06 10:41 ` Michael Olbrich
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=1406734093.22823.134.camel@coredoba.hi.pengutronix.de \
--to=jlu@pengutronix.de \
--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