From: Jeremy Rosen <jeremy.rosen@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] add new package fxload
Date: Tue, 06 Nov 2012 09:58:28 +0100 (CET) [thread overview]
Message-ID: <27204261.196.1352192268013.JavaMail.rosen@pcrosen> (raw)
In-Reply-To: <5098536C.5060903@mind.be>
>
> 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.
>
ok, i'll do take two of the patch using git-send-email, but I'm struggling a bit with the smtp server here at work. I'll try to get it to work...
> 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)
>
> 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.
ok, will do .
BTW, your link is dead, a minute of googling and I found
http://elinux.org/Developer_Certificate_Of_Origin
and
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/SubmittingPatches
which might be the same thing or close enough to point people to the next time my noob question is asked
>
> 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.
>
I am a bit confused how the text of the message I give to git-send-email mix up with the commit message,
should I just put my personal text after the --- line directly in the commit message (before git-send-email) ?
[snip : comments on the patch itself]
ok, i will do all that for V2
>
> Overall, it looks very good, though. Congratulations!
>
thanks, V2 will be even better :D
next prev parent reply other threads:[~2012-11-06 8:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1781554.153.1352137532474.JavaMail.rosen@pcrosen>
2012-11-05 17:48 ` [Buildroot] [PATCH] add new package fxload Jeremy Rosen
2012-11-06 0:01 ` Arnout Vandecappelle
2012-11-06 8:58 ` Jeremy Rosen [this message]
2012-11-06 15:33 ` Alex Bradbury
2012-11-07 0:21 ` Arnout Vandecappelle
2012-11-06 10:50 Jérémy Rosen
2012-11-07 0:23 ` Arnout Vandecappelle
2012-11-07 9:49 ` Peter Korsgaard
2012-11-07 10:00 ` Jeremy Rosen
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=27204261.196.1352192268013.JavaMail.rosen@pcrosen \
--to=jeremy.rosen@openwide.fr \
--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