Hello Michael,
On Wed, Aug 06, 2014 at 09:04:13AM +0200, Michael Olbrich wrote:
On Thu, Jul 31, 2014 at 09:44:16AM +0200, Uwe Kleine-König wrote:
On Thu, Jul 31, 2014 at 09:33:02AM +0200, Juergen Borleis wrote:
On Thursday 31 July 2014 09:14:25 Uwe Kleine-König wrote:
[...]
Compared
On Wed, Aug 06, 2014 at 09:28:56AM +0200, Uwe Kleine-König wrote:
On Wed, Aug 06, 2014 at 09:04:13AM +0200, Michael Olbrich wrote:
On Thu, Jul 31, 2014 at 09:44:16AM +0200, Uwe Kleine-König wrote:
On Thu, Jul 31, 2014 at 09:33:02AM +0200, Juergen Borleis wrote:
On Thursday 31 July 2014
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
Hello,
On Wed, Jul 30, 2014 at 12:20:03PM +0200, Juergen Borleis wrote:
Some use cases are using the barebox's built-in environment only, but still
provide an external environment store to save a modified environment (for
development purposes for example).
In this case barebox works as
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.
I
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
Hi Uwe,
On Thursday 31 July 2014 09:44:16 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
Some use cases are using the barebox's built-in environment only, but still
provide an external environment store to save a modified environment (for
development purposes for example).
In this case barebox works as intended even if the external store is empty
and thus invalid. But even if it is an
Add a simple flag to envfs to be able to mark an external environment as
not to be used.
This change should not affect existing systems, because the current envfs
implementation ensures the 'flags' member in the envfs master block is always
zeroed.
Signed-off-by: Juergen Borleis
Some use cases are using the barebox's built-in environment only, but still
provide an external environment store to save a modified environment (for
development purposes for example).
In this case barebox works as intended even if the external store is empty
and thus invalid. But even if it is an
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
On Wed, Jul 30, 2014 at 05:28:13PM +0200, Jan Lübbe wrote:
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
12 matches
Mail list logo
