From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] curlftpfs: new package
Date: Sat, 21 Jul 2012 17:31:44 +0200 [thread overview]
Message-ID: <20120721173144.1f50021f@skate> (raw)
In-Reply-To: <1342884438-5325-1-git-send-email-rbraun@sceen.net>
Le Sat, 21 Jul 2012 17:27:18 +0200,
Richard Braun <rbraun@sceen.net> a ?crit :
> @@ -169,6 +169,7 @@ menu "Hardware handling"
> source "package/acpid/Config.in"
> source "package/cdrkit/Config.in"
> source "package/cramfs/Config.in"
> +source "package/curlftpfs/Config.in"
> source "package/dbus/Config.in"
> source "package/dbus-glib/Config.in"
> source "package/dbus-python/Config.in"
This "Hardware handling" menu is becoming quite crazy. curlftpfs
clearly has nothing to do with Hardware handling (and many other things
in there).
Even "cramfs" for example is not quite Hardware handling related. Maybe
we should put more things in the "System tools" menu, or create a
"Filesystems tools" menu or something. Suggestions welcome.
Otherwise, looks good.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-07-21 15:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-21 15:27 [Buildroot] [PATCH] curlftpfs: new package Richard Braun
2012-07-21 15:31 ` Thomas Petazzoni [this message]
2012-07-21 16:11 ` Richard Braun
2012-07-24 11:44 ` [Buildroot] [PATCH v2] " Richard Braun
2012-07-30 14:09 ` [Buildroot] [PATCH v3] " Richard Braun
2012-07-30 14:37 ` Thomas Petazzoni
2012-07-30 16:12 ` [Buildroot] [PATCH v4] " Richard Braun
2012-07-21 19:36 ` [Buildroot] [PATCH] " Gustavo Zacarias
-- strict thread matches above, loose matches on Subject: below --
2012-10-30 13:35 Alexander Varnin
2012-10-30 13:44 ` Alexander Varnin
2013-01-14 21:37 ` Peter Korsgaard
2013-01-14 21:54 ` Richard Braun
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=20120721173144.1f50021f@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