From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 04/19] nspr: update to 4.12
Date: Wed, 2 Mar 2016 16:18:20 +0200 [thread overview]
Message-ID: <56D6F62C.2020000@linux.intel.com> (raw)
In-Reply-To: <CAMKF1sqDVjNH_XLhbY+86BdFx9vZZpaw8j-XNDTM67st=LWW=Q@mail.gmail.com>
On 03/01/2016 04:58 PM, Khem Raj wrote:
>> The failing patch is applied only when musl is in use (and so the regression
>> went unnoticed). Can you rework it so that it can be applied
>> unconditionally?
>
> This probably could be however OE-Core supports musl and poky-tiny
> defaults to it. It will be good to test
> changes for it when changing OE-Core at the least bitbake -cpatch <recipe>
Yes, but that's a job for autobuilder, I'm afraid. When doing local
changes, I have to draw the line somewhere about what I test, and what I
don't, and testing builds against various libc providers is outside of that.
Generally, patches should be unconditional, because a) we should be able
to send them upstream, b) conditional patches create several slightly
different versions of source code, which is a maintenance headache.
Alex
next prev parent reply other threads:[~2016-03-02 14:22 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 15:59 [PATCH 00/19] Recipe version updates Alexander Kanavin
2016-02-25 15:59 ` [PATCH 01/19] epiphany: update to 3.18.4 Alexander Kanavin
2016-02-25 15:59 ` [PATCH 02/19] libfm: update to 1.2.4 Alexander Kanavin
2016-02-25 15:59 ` [PATCH 03/19] pcmanfm: " Alexander Kanavin
2016-02-25 15:59 ` [PATCH 04/19] nspr: update to 4.12 Alexander Kanavin
2016-02-29 18:39 ` Khem Raj
2016-03-01 14:14 ` Alexander Kanavin
2016-03-01 14:58 ` Khem Raj
2016-03-02 14:18 ` Alexander Kanavin [this message]
2016-03-02 14:30 ` Khem Raj
2016-03-02 15:23 ` Richard Purdie
2016-03-02 15:55 ` Martin Jansa
2016-03-03 13:12 ` Flanagan, Elizabeth
2016-02-25 15:59 ` [PATCH 05/19] ffmpeg: update to 3.0 Alexander Kanavin
2016-02-25 15:59 ` [PATCH 06/19] libsolv: update to 0.6.19 Alexander Kanavin
2016-02-25 15:59 ` [PATCH 07/19] ccache: update to 3.2.4 Alexander Kanavin
2016-02-25 15:59 ` [PATCH 08/19] clutter-gst-3.0: update to 3.0.16 Alexander Kanavin
2016-02-25 15:59 ` [PATCH 09/19] gnupg: update to 2.1.11 Alexander Kanavin
2016-02-25 15:59 ` [PATCH 10/19] git: update to 2.7.2 Alexander Kanavin
2016-02-25 15:59 ` [PATCH 11/19] gtk-icon-utils-native: update to 3.18.8 Alexander Kanavin
2016-02-25 15:59 ` [PATCH 12/19] gtk+3: " Alexander Kanavin
2016-02-25 15:59 ` [PATCH 13/19] libdrm: update to 2.4.67 Alexander Kanavin
2016-02-25 15:59 ` [PATCH 14/19] ncurses: update to revision 20160213 Alexander Kanavin
2016-02-25 15:59 ` [PATCH 15/19] nettle: update to 3.2 Alexander Kanavin
2016-02-25 15:59 ` [PATCH 16/19] pax-utils: update to 1.1.5 Alexander Kanavin
2016-02-25 15:59 ` [PATCH 17/19] python-git: update to 1.0.2 Alexander Kanavin
2016-02-25 15:59 ` [PATCH 18/19] vala: update to 0.30.1 Alexander Kanavin
2016-02-25 15:59 ` [PATCH 19/19] shared-mime-info: update to 1.6 Alexander Kanavin
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=56D6F62C.2020000@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@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.