Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] barebox: add an option to embed environment image
Date: Thu, 5 May 2016 19:30:14 +0200	[thread overview]
Message-ID: <20160505193014.59240f3b@free-electrons.com> (raw)
In-Reply-To: <CAGm1_ktZovu04emMf9Xgpm4EadvnVttude3atO98zzii1CEgew@mail.gmail.com>

Hello,

On Thu, 5 May 2016 17:17:54 +0200, Yegor Yefremov wrote:

> We've already discussed this. Both images can be useful together.
> Embedded image contains recovery scripts and external image real
> scripts, variables. For example at production stage you don't have
> external image, so embedded one takes care, after production external
> image will be used and so on.

OK. Sorry for asking the same question again, there's so many different
topics going on at the same time that I easily lose track of previous
discussions. Whenever this sort of discussion happens, it's a good idea
to improve the commit log in the next iterations of the patch with the
result of the discussion. Not only this avoids getting asked the same
questions, but it also means that the discussion/reasoning gets kept in
the Git history, which might prove useful in the future.

Can you nonetheless resend a v4 with the minor improvements suggested
by Arnout (and possibly with an improved commit log explaining why we
need to support both an "external" environment and an "embedded"
environment) ?

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2016-05-05 17:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-04 11:14 [Buildroot] [PATCH v3] barebox: add an option to embed environment image yegorslists at googlemail.com
2016-05-04 19:46 ` Arnout Vandecappelle
2016-05-05 13:56 ` Thomas Petazzoni
2016-05-05 15:17   ` Yegor Yefremov
2016-05-05 17:30     ` Thomas Petazzoni [this message]
2016-05-05 19:02       ` Yegor Yefremov

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=20160505193014.59240f3b@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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