From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] micropython: bump version to v1.9.3
Date: Mon, 16 Apr 2018 17:44:23 +0200 [thread overview]
Message-ID: <20180416174423.2a0e1c2e@windsurf.numericable.fr> (raw)
In-Reply-To: <1523885614.4244.5.camel@flir.com>
Hello,
On Mon, 16 Apr 2018 13:28:47 +0000, Blomme, Maarten wrote:
> (With correct formatting now)
>
> The build step now requires building mpy-cross first.
>
> Signed-off-by: Blomme, Maarten <Maarten.Blomme@flir.com>
> ---
> package/micropython-lib/micropython-lib.hash | 2 +-
> package/micropython-lib/micropython-lib.mk | 2 +-
> package/micropython/micropython.hash | 2 +-
> package/micropython/micropython.mk | 7 ++++---
> 4 files changed, 7 insertions(+), 6 deletions(-)
I fixed up the breakage caused by your e-mail client or e-mail server,
and applied. Sadly in the process I forgot to adjust your commit log to
remove the "(With correct formatting now)" message, which shouldn't be
part of the commit log. Such messages should be placed below the "---"
marker after the Signed-off-by line. This way, they are part of the
e-mail being sent, but not considered by git as a part of the commit
log.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-04-16 15:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 13:28 [Buildroot] [PATCH 1/1] micropython: bump version to v1.9.3 Blomme, Maarten
2018-04-16 14:01 ` Thomas Petazzoni
2018-04-16 15:44 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-04-16 8:09 Blomme, Maarten
2018-04-16 12:22 ` Thomas Petazzoni
2018-04-16 13:30 ` Blomme, Maarten
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=20180416174423.2a0e1c2e@windsurf.numericable.fr \
--to=thomas.petazzoni@bootlin.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