All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/vpnc: fix musl build
Date: Thu, 11 Feb 2016 00:07:43 +0100	[thread overview]
Message-ID: <20160211000743.33a1e73f@free-electrons.com> (raw)
In-Reply-To: <1453640456-32346-1-git-send-email-bernd.kuhls@t-online.de>

Dear Bernd Kuhls,

On Sun, 24 Jan 2016 14:00:56 +0100, Bernd Kuhls wrote:
> The autobuilders did not catch the error yet because they failed
> earlier with other packages, but I am continuing the build based
> on the defconfig from:
> http://autobuild.buildroot.net/results/6cc/6cc0f8c067e07deea688b9b97284601a596b898c/
> 
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>

Once again, those patches really didn't had a proper commit log, so I
don't want to merge something like this. Yes the other existing patches
for vpnc are crappy, but it's not a reason to add more of them.

So instead, I've sent a series which updates the vpnc package,
reformats the patch with Git, splits them properly, adds proper commit
logs, and I submitted a pull request upstream.

See:

  http://lists.busybox.net/pipermail/buildroot/2016-February/152495.html

Could you review all the pending musl fix patches from you that are in
patchwork, and try to rework the ones where the musl patches don't
have a proper commit log. Hint: if the commit log is just "musl fix",
then it's wrong. If the commit makes it work for musl, but is otherwise
non-upstreamable, it's wrong.

It would really help if you could clean up some of those patches. We do
want to fix musl related issues, but not at the expense of having
unclean patches added in Buildroot.

Thanks a lot,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2016-02-10 23:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-24 13:00 [Buildroot] [PATCH 1/1] package/vpnc: fix musl build Bernd Kuhls
2016-02-10 23:07 ` 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=20160211000743.33a1e73f@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 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.