All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: any reason why sandbox (and other defconfigs) don't enable MAGICVAR?
Date: Wed, 2 Jul 2014 14:52:37 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.11.1407021450110.4107@localhost> (raw)


  was playing with a sandbox build and noticed that the default
sandbox config doesn't select MAGICVAR -- any reason why not? on a
larger scale, it seems odd that quite a number of defconfigs select
MAGICVAR (and MAGICVAR_HELP), while others don't.

  is this a per-machine selection? it just seems that it should be
more consistent -- that fundamental features like MAGICVAR should
either be all on or all off by default. thoughts?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

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

             reply	other threads:[~2014-07-02 18:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-02 18:52 Robert P. J. Day [this message]
2014-07-03  5:38 ` any reason why sandbox (and other defconfigs) don't enable MAGICVAR? Sascha Hauer

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=alpine.LFD.2.11.1407021450110.4107@localhost \
    --to=rpjday@crashcourse.ca \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.