From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/musepack: fix musl build
Date: Sun, 7 Feb 2016 22:44:32 +0100 [thread overview]
Message-ID: <20160207224432.4532ebc0@free-electrons.com> (raw)
In-Reply-To: <1454142700-9293-1-git-send-email-bernd.kuhls@t-online.de>
Dear Bernd Kuhls,
On Sat, 30 Jan 2016 09:31:40 +0100, Bernd Kuhls wrote:
> Fixes
> http://autobuild.buildroot.net/results/6eb/6ebc9cbee3fc48f4f5b658d11b040ad62fb6607f/
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> package/musepack/0003-musl.patch | 24 ++++++++++++++++++++++++
> 1 file changed, 24 insertions(+)
> create mode 100644 package/musepack/0003-musl.patch
I've applied, but to be honest, I almost rejected your patch:
1/ The musepack patch does two completely different things, they
should have been two separate patches.
2/ "Fix musl" is not a proper patch description. Due to this, I have
to dig myself again in the issue, to understand what was the
problem, and how your patch fixes it. Please add a proper
description to each and every patch. "Fix musl" is *not* a good
description.
See
https://git.busybox.net/buildroot/commit/package/musepack?id=5f3aed3f50ff48c8a60185407d7220aeedfea5e5
for the type of description that we need to have.
Don't get me wrong: I definitely appreciate your effort to fix numerous
musl build failures. But with such short descriptions, I have to
basically re-do all the investigation you have already done... which
means I spend as much time as you have done. Could you please help by
writing longer patch descriptions ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-02-07 21:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-30 8:31 [Buildroot] [PATCH 1/1] package/musepack: fix musl build Bernd Kuhls
2016-02-07 21:44 ` 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=20160207224432.4532ebc0@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