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 4/5] zsh: alpha sort menu option
Date: Tue, 3 Dec 2013 09:50:20 +0100	[thread overview]
Message-ID: <20131203095020.2a02cf8f@skate> (raw)
In-Reply-To: <87iov6pd8f.fsf@dell.be.48ers.dk>

Dear Peter Korsgaard,

On Tue, 03 Dec 2013 09:09:36 +0100, Peter Korsgaard wrote:
> >>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:
> 
>  > Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
>  > ---
>  >  package/Config.in | 4 +++-
>  >  1 file changed, 3 insertions(+), 1 deletion(-)
> 
>  > diff --git a/package/Config.in b/package/Config.in
>  > index a65ceac..e70a58c 100644
>  > --- a/package/Config.in
>  > +++ b/package/Config.in
>  > @@ -932,7 +932,6 @@ source "package/at/Config.in"
>  >  if BR2_PACKAGE_BUSYBOX_SHOW_OTHERS
>  >  source "package/bash/Config.in"
>  >  source "package/dash/Config.in"
>  > -source "package/zsh/Config.in"
> 
> You are right, certainly - But I think it is more userfriendly to make
> an exception and keep all the shells together.
> 
> What do others think?

Ideas:

 * Instead of "Shell and utilities", have two menus: "Shell" and
   "Utilities".

 * In the "Shell and utilities" menu, create two sub-sections,
   separated by comments:

comment "Shells"
... some packages ...

comment "Utilities"
... some packages ...

Best regards,

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

  reply	other threads:[~2013-12-03  8:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-02 10:49 [Buildroot] [PATCH 1/5] coreutils: belongs to system tools, not development Gustavo Zacarias
2013-12-02 10:49 ` [Buildroot] [PATCH 2/5] coreutils: bump to version 8.21 Gustavo Zacarias
2013-12-03  8:07   ` Peter Korsgaard
2013-12-02 10:49 ` [Buildroot] [PATCH 3/5] util-linux: add agetty->getty symlink Gustavo Zacarias
2013-12-03  8:08   ` Peter Korsgaard
2013-12-02 10:49 ` [Buildroot] [PATCH 4/5] zsh: alpha sort menu option Gustavo Zacarias
2013-12-03  8:09   ` Peter Korsgaard
2013-12-03  8:50     ` Thomas Petazzoni [this message]
2013-12-03 10:23       ` Gustavo Zacarias
2013-12-03 10:28         ` Peter Korsgaard
2013-12-03 10:28       ` Peter Korsgaard
2013-12-02 10:49 ` [Buildroot] [PATCH 5/5] sysklogd: install to /sbin Gustavo Zacarias
2013-12-03  8:12   ` Peter Korsgaard
2013-12-03  8:01 ` [Buildroot] [PATCH 1/5] coreutils: belongs to system tools, not development Peter Korsgaard
2013-12-03  8:08   ` Jeremy Rosen
2013-12-03 10:17     ` Gustavo Zacarias
2013-12-03 10:32       ` Peter Korsgaard
2013-12-03  8:59   ` Thomas Petazzoni
2013-12-03 10:05     ` Peter Korsgaard
2013-12-03 10:12       ` Thomas Petazzoni
2013-12-03 10:34         ` Peter Korsgaard
2013-12-03 10:08     ` Gustavo Zacarias

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=20131203095020.2a02cf8f@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