From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] python3: switch to Git formatted patches
Date: Mon, 4 Jan 2016 22:55:04 +0100 [thread overview]
Message-ID: <568AEA38.1020509@mind.be> (raw)
In-Reply-To: <1451931809-24511-1-git-send-email-thomas.petazzoni@free-electrons.com>
On 04-01-16 19:23, Thomas Petazzoni wrote:
> In preparation for the bump to Python 3.5.0, let's switch all the
> patches to the Git format. This way, a Git repository of the Python
> source code can be used to manage those patches, which makes it easier
> to bump to newer Python versions.
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Didn't test, but verified that all patches are retained, are numbered the same,
that the patch itself hasn't changed, and that the new authorship is correct.
Regards,
Arnout
[snip]
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2016-01-04 21:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 18:23 [Buildroot] [PATCH 1/2] python3: switch to Git formatted patches Thomas Petazzoni
2016-01-04 18:23 ` [Buildroot] [PATCH 2/2] python3: bump to 3.5.1 Thomas Petazzoni
2016-01-04 22:35 ` Arnout Vandecappelle
2016-04-28 21:58 ` Thomas Petazzoni
2016-05-02 21:14 ` Arnout Vandecappelle
2016-01-06 8:34 ` Christophe Vu-Brugier
2016-01-06 8:47 ` Yegor Yefremov
2016-01-04 21:02 ` [Buildroot] [PATCH 1/2] python3: switch to Git formatted patches Peter Korsgaard
2016-01-04 21:39 ` Arnout Vandecappelle
2016-01-04 21:50 ` Peter Korsgaard
2016-01-04 21:55 ` Arnout Vandecappelle [this message]
2016-01-04 23:13 ` Peter Korsgaard
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=568AEA38.1020509@mind.be \
--to=arnout@mind.be \
--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