mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Uwe Kleine-K??nig <u.kleine-koenig@pengutronix.de>
Cc: barebox@lists.infradead.org, Juergen Borleis <jbe@pengutronix.de>
Subject: Re: envfs: provide an intentional way to ignore an existing external environment
Date: Wed, 6 Aug 2014 05:56:07 +0200	[thread overview]
Message-ID: <20140806035607.GF19147@ns203013.ovh.net> (raw)
In-Reply-To: <20140731074416.GR6146@pengutronix.de>

On 09:44 Thu 31 Jul     , Uwe Kleine-K??nig wrote:
> 
> On Thu, Jul 31, 2014 at 09:33:02AM +0200, Juergen Borleis wrote:
> > Hi Uwe,
> > 
> > On Thursday 31 July 2014 09:14:25 Uwe Kleine-König wrote:
> > > [...]
> > > Compared with storing the default environment in the external store the
> > > only difference is that you don't need to modify it if you change the
> > > internal one, right?
> > 
> > This would also be an advantage of this new feature.
> The only one even?
> 
> > > I wonder what the targeted use case is.
> > 
> > To use an external stored environment *only* for development purposes or tests 
> > and to keep the possibility to do so.
> Doesn't make a warm and cosy feeling. Isn't it easier and more robust to
> just not tell barebox about the external storage at all and for the
> testing/development procedure do an explicit
> 
> 	loadenv /dev/tralala
+1

Best Regards,
J.

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  parent reply	other threads:[~2014-08-06  3:52 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 ` envfs: provide an intentional way to ignore an existing external environment Jan Lübbe
2014-07-30 21:09   ` 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 [this message]
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=20140806035607.GF19147@ns203013.ovh.net \
    --to=plagnioj@jcrosoft.com \
    --cc=barebox@lists.infradead.org \
    --cc=jbe@pengutronix.de \
    --cc=u.kleine-koenig@pengutronix.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