From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/Config.in: order alphabetically
Date: Tue, 1 Oct 2013 23:31:35 +0200 [thread overview]
Message-ID: <20131001233135.7a011a18@skate> (raw)
In-Reply-To: <2fd3fbf902d87dab33eb.1380096103@argentina>
Dear Thomas De Schampheleire,
On Wed, 25 Sep 2013 10:01:43 +0200, Thomas De Schampheleire wrote:
> Even though new packages are normally added in the right alphabetical order,
> there still remain quite a number of incorrect orderings in package/Config.in.
> In this patch, alphabetical order is created in each menu.
>
> Note that this sometimes mean that packages that logically belong together, like
> cups, gutenprint, hplip, are now split apart.
>
> Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
--
Thomas Petazzoni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-01 21:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 8:01 [Buildroot] [PATCH] package/Config.in: order alphabetically Thomas De Schampheleire
2013-10-01 21:31 ` Thomas Petazzoni [this message]
2013-10-06 20:54 ` Peter Korsgaard
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=20131001233135.7a011a18@skate \
--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