From: Sascha Hauer <s.hauer@pengutronix.de>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v2] at91: reorder BOARDINFO alphabetically
Date: Fri, 7 Dec 2012 09:30:12 +0100 [thread overview]
Message-ID: <20121207083012.GB10369@pengutronix.de> (raw)
In-Reply-To: <20121207065249.GK8327@game.jcrosoft.org>
On Fri, Dec 07, 2012 at 07:52:49AM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 12:16 Thu 06 Dec , Fabio Porcedda wrote:
> > This is to have a nicely ordered list and to decrease the
> > likelihood of a conflict when adding a new board.
> >
> > Signed-off-by: Fabio Porcedda <fabio.porcedda@gmail.com>
> > Cc: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
> > ---
> > v2:
> NAK
>
> I order them by Kconfig keepo it that way
I'd say it makes more sense to keep them in the order the user actually
sees them, it makes it easier to find the entries. What's the value in
ordering them by Kconfig name?
If you order them by Kconfig name, the Calao boards end up in three
different places in the user visible view.
Sascha
--
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:[~2012-12-07 8:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 11:16 Fabio Porcedda
2012-12-06 20:03 ` Sascha Hauer
2012-12-07 6:52 ` Jean-Christophe PLAGNIOL-VILLARD
2012-12-07 8:30 ` Sascha Hauer [this message]
2012-12-07 8:49 ` Fabio Porcedda
2012-12-07 20:06 ` Jean-Christophe PLAGNIOL-VILLARD
2012-12-08 11:01 ` 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=20121207083012.GB10369@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=plagnioj@jcrosoft.com \
/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