From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/Config.in: order alphabetically
Date: Sun, 06 Oct 2013 22:54:54 +0200 [thread overview]
Message-ID: <87siwece75.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <2fd3fbf902d87dab33eb.1380096103@argentina> (Thomas De Schampheleire's message of "Wed, 25 Sep 2013 10:01:43 +0200")
>>>>> "Thomas" == Thomas De Schampheleire <patrickdepinguin@gmail.com> writes:
Thomas> Even though new packages are normally added in the right
Thomas> alphabetical order, there still remain quite a number of
Thomas> incorrect orderings in package/Config.in. In this patch,
Thomas> alphabetical order is created in each menu.
Thomas> Note that this sometimes mean that packages that logically
Thomas> belong together, like cups, gutenprint, hplip, are now split
Thomas> apart.
Thomas> Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
Committed with some fixups now that we've added more packages, thanks.
Thomas> For the vim users out there: do you know the 'filter' command?
Thomas> This allows to take content from the document, pipe it through
Thomas> a shell pipeline of your choosing, and put the output back in
Thomas> the document in place of the original text. For example:
Thomas> :'<,'>! sort will replace the visual selection with its sorted
Thomas> version. There exist also 'read!' and 'write!' commands that
Thomas> do more or less half of the filter command: read takes output
Thomas> from a shell pipeline and pastes it in the document, but does
Thomas> not use any input from the document. The write command uses
Thomas> text from the document as input for the shell pipeline, but
Thomas> discards the output. See :help filter, :help read!, :help
Thomas> write!
Yeah, emacs has it as well (M-| cmd)
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2013-10-06 20:54 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
2013-10-06 20:54 ` Peter Korsgaard [this message]
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=87siwece75.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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