From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Question about Patch submission
Date: Fri, 31 Jan 2014 14:06:05 +0100 [thread overview]
Message-ID: <20140131130605.EBD4038554E@gemini.denx.de> (raw)
In-Reply-To: <52EB892C.6090201@petermaier.org>
Dear Hannes,
In message <52EB892C.6090201@petermaier.org> you wrote:
>
> I have allready read the patch submission rules on the u-boot website.
> But it is still not clear to me how i do the whole thing.
[1] gives pretty detailed instructions; it even icludes explicit
hints how to create and submit patches - search for example for "The
best way the generate patches ..." If anything is not clean, then
please ask what exactly you do not understand.
> How should i take up the differences and how they are posted ?
See [1].
> Actually the idea in my head looks like this:
>
> a) fetch most current u-boot from
> http://git.denx.de/cgi-bin/gitweb.cgi?p=u-boot.git;a=summary
> b) using 'diff' for getting the patch:
>
> diff u-boot/include/i2c.h u-boot-current/include/i2c.h
> 70c70
> < int speed;
> ---
> > int speed, waitdelay;
No, that would be totally useless. If using diff, then at least make
sure to provide a context diff. But as documented, you should rather
use "git format-patch".
> and so on ...
> pasting all the outputs into an email which passes to the rules given on
> the website.
Copying & pasting is a pretty rteliable way to cause white-space
garbled patches. This will not work.
> at the end give the signed-off-by statement.
No, this belongs to the commit message, and not at the end.
> Are iam right in this ?
No. Please read [1].
[1] http://www.denx.de/wiki/U-Boot/Patches
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Any time things appear to be going better, you have overlooked some-
thing.
prev parent reply other threads:[~2014-01-31 13:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 11:29 [U-Boot] Question about Patch submission Hannes Petermaier
2014-01-31 13:06 ` Wolfgang Denk [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=20140131130605.EBD4038554E@gemini.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.de \
/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