From: Andrei Gherzan <andrei@gherzan.ro>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-networking][PATCH] networkmanager: Update to 1.18.0
Date: Tue, 28 May 2019 16:37:49 +0100 [thread overview]
Message-ID: <119819b9-eee8-442e-f4bd-b4005b0a1a6d@gherzan.ro> (raw)
In-Reply-To: <CAMKF1srfV74+4jODJtnOtgKwSBtBgznGENOZFOvkp+vZ7BdAoQ@mail.gmail.com>
On 28/05/2019 16.13, Khem Raj wrote:
> Hi Andrei
>
> The musl patches need to be forward ported as well. They dont apply
> cleanly anymore on top of this update.
Seems like. So all the contributions now need to go through local musl
and glibc testing? This sounds a little bit of an overhead and might
discourage people in contributing because usually everyone is working on
one libc variant. Just raising it as a concern. As per this specific
case, I'm going to fix it and push a V2.
--
Andrei Gherzan
gpg: rsa4096/D4D94F67AD0E9640 | t: @agherzan
next prev parent reply other threads:[~2019-05-28 15:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 13:13 [meta-networking][PATCH] networkmanager: Update to 1.18.0 Andrei Gherzan
2019-05-28 15:13 ` Khem Raj
2019-05-28 15:37 ` Andrei Gherzan [this message]
2019-05-28 16:14 ` Khem Raj
2019-05-28 18:06 ` Adrian Bunk
2019-05-28 18:46 ` Andrei Gherzan
2019-05-28 20:37 ` Khem Raj
2019-05-28 21:20 ` Adrian Bunk
2019-05-29 9:04 ` Khem Raj
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=119819b9-eee8-442e-f4bd-b4005b0a1a6d@gherzan.ro \
--to=andrei@gherzan.ro \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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.