From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv3] wine: Bump to version 1.8.1
Date: Mon, 8 Feb 2016 21:21:57 +0100 [thread overview]
Message-ID: <20160208212157.533df7f7@free-electrons.com> (raw)
In-Reply-To: <56B8DCC1.9080203@dawncrow.de>
Dear Andr? Hentschel,
On Mon, 8 Feb 2016 19:21:53 +0100, Andr? Hentschel wrote:
> Bumping to stable version 1.8.1
>
> Upstreamed patch is finally dropped.
>
> Signed-off-by: Andr? Hentschel <nerv@dawncrow.de>
> ---
> try2: removing autoreconf, thanks to Thomas for reviewing
> try3: resend
Thanks, but we don't take patches as attached files, since we cannot
easily review them.
Why don't you send patches with git send-email, as I suggested, and as
is suggested in the Buildroot manual?
Yes, it requires a little bit of time to configure git send-email, but
you will 1/ have patches properly formatted and 2/ save a lot of time
when sending patch series.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-02-08 20:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 18:21 [Buildroot] [PATCHv3] wine: Bump to version 1.8.1 André Hentschel
2016-02-08 20:21 ` Thomas Petazzoni [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=20160208212157.533df7f7@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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