Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] libsolv: correctly attribute musl fixing patches
Date: Tue, 11 Apr 2017 13:25:23 +0300	[thread overview]
Message-ID: <8c478a3d-e1cd-d46f-a5d3-434492520342@linux.intel.com> (raw)
In-Reply-To: <1636904.5z37o6m8AP@peggleto-mobl.ger.corp.intel.com>

On 04/11/2017 01:15 PM, Paul Eggleton wrote:
> On Tuesday, 11 April 2017 9:22:43 PM NZST Alexander Kanavin wrote:
>> Also, they were previously squashed into a single patch; restore
>> the original two-patch arrangement.
>
> Didn't Mark H just send a patch to fix this?

Mark's patch incorrectly changes the recipe patch so that it doesn't 
apply to upstream source anymore (the stuff in CMakeLists.txt, I think).


Alex



      reply	other threads:[~2017-04-11 10:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-11  9:22 [PATCH] libsolv: correctly attribute musl fixing patches Alexander Kanavin
2017-04-11 10:15 ` Paul Eggleton
2017-04-11 10:25   ` Alexander Kanavin [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=8c478a3d-e1cd-d46f-a5d3-434492520342@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox