add new package fxload

Hello everybody

I recently had to add a small utility called fxload to buildroot

fxload is provided by the linux-hotplug project and is used to upload firmware into usb device it is generally used as a helper function by udev.

This is my first patch to buildroot, so feel free to tell me if I didn't follow the proper protocol, I will gladly correct and resubmit

Regards
J?r?my Rosen

fight key loggers : write some perl using vim

0001-add-new-package-fxload.patch

From a1d3bdcf48851dedeca9597816135f4c1589e37a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=A9r=C3=A9my=20Rosen?=<[email protected]>
Date: Fri, 2 Nov 2012 11:43:42 +0100
Subject: [PATCH] add new package fxload

---
  package/Config.in        |    1 +
  package/fxload/Config.in |    9 +++++++++
  package/fxload/fxload.mk |   20 ++++++++++++++++++++
  3 files changed, 30 insertions(+)

create mode 100644 package/fxload/Config.in
create mode 100644 package/fxload/fxload.mk

package/Config.in +1 -0

index 1df099b..f72a34b 100644
@@ -211,6 +211,7 @@ source "package/flashrom/Config.in"
  source "package/fconfig/Config.in"
  source "package/fis/Config.in"
  source "package/fmtools/Config.in"
+source "package/fxload/Config.in"
  source "package/gadgetfs-test/Config.in"
  source "package/gdisk/Config.in"
  source "package/gpsd/Config.in"

package/fxload/Config.in new file +0 -0

new file mode 100644
index 0000000..6fc28a7

Here goes...

First of all, we prefer the patches to be sent in-line rather than as
attachment. That makes it easier to review by just replying to the mail.
git send-email is the easiest way to contribute.

Also I'll warn you: it may take a while (months) before your patch is
accepted even if you make all necessary correction, and we may even forget
to include it in the end. That's not because we're evil :-) but because
our contribution process is still sub-optimal. Buildroot has grown significantly in number of contributions over the last two years, and our maintainer (Peter Korsgaard) is just saturated. We're still experimenting
with ways to improve the process.

Add a Signed-off-by line for yourself. This is a short way for you to
assert that you are entitled to contribute the patch under buildroot's
GPL license. See http://kerneltrap.org/files/Jeremy/DCO.txt for more
details.

BTW, if you want to add additional comments that aren't supposed to
go in the git log message (e.g. "this is my first patch, please give feedback", add it below the Signed-off-by line, separated by ---. Then git-am will remove that part automatically. If you send an updated patch, it's nice if you can write in this comment section what
changed compared to the first one. So typically you'll see:

Signed-off-by ...

---
v2: Incorporated comments from Arnout, except for the foo because blah.

Overall, it looks very good, though. Congratulations!

Quoted 12 lines

Also I'll warn you: it may take a while (months) before your patch is
accepted even if you make all necessary correction, and we may even forget
to include it in the end. That's not because we're evil :-) but because
our contribution process is still sub-optimal. Buildroot has grown significantly in number of contributions over the last two years, and our maintainer (Peter Korsgaard) is just saturated. We're still experimenting
with ways to improve the process.

Fair enough, i'm a maintainer for other FOSS projects, so I know how that sort of problem go...

is Peter the only one comitting ? couldn't someone help with simple patches (like updating version of existing packages)

Quoted 7 lines

Add a Signed-off-by line for yourself. This is a short way for you

Quoted 6 lines

to
assert that you are entitled to contribute the patch under buildroot's
GPL license. Seehttp://kerneltrap.org/files/Jeremy/DCO.txt for more
details.

ok, will do .

BTW, your link is dead, a minute of googling and I found

http://elinux.org/Developer_Certificate_Of_Origin