From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] my recent i2c patches
Date: Wed, 24 Feb 2010 21:31:52 +0100 [thread overview]
Message-ID: <20100224203152.A4880EBA92F@gemini.denx.de> (raw)
In-Reply-To: <ac9c93b11002241132j50c1c4a2p5e4407da7f096324@mail.gmail.com>
Dear Frans Meulenbroeks,
In message <ac9c93b11002241132j50c1c4a2p5e4407da7f096324@mail.gmail.com> you wrote:
> One word wrt the i2c patches I just mailed.
> It was my impression that git send-email would include the number in
> the patch but as can be seen that was not the case.
Git-send-email does not insert anything, it just sends the emails.
If you want numbered patches, you have to add the numbers when
formatting the patches - i. e. use "git-format-patch -n"
> The patches are to be applied in the following order:
> 0001-cmd_i2c.c-reduced-subaddress-length-to-3-bytes.patch
> 0002-cmd_bootm.c-made-subcommand-array-static.patch
> 0003-cmd_i2c.c-reworked-subcommand-handling.patch
> 0004-cmd_i2c.c-sorted-commands-alphabetically.patch
> 0005-cmd_i2c.c-added-i2c-read-to-memory-function.patch
Thanks.
> PS: I once read somewhere that it is also possible to add additional
> text in a patch only for the mailing list, so not part of the commit
> message.
Indeed. Text below the "---" line is comment.
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
Good manners are the settled medium of social, as specie is of
commercial, life; returns are equally expected for both.
- Lord Chesterfield _Letters to his Son_, 25 December 1753
prev parent reply other threads:[~2010-02-24 20:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 19:32 [U-Boot] my recent i2c patches Frans Meulenbroeks
2010-02-24 19:51 ` Eric Bénard
2010-02-24 20:31 ` 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=20100224203152.A4880EBA92F@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.