From: Patrick Ohly <patrick.ohly@intel.com>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: Mike Crowe <mac@mcrowe.com>, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] mtd-utils: Upgrade to 2.0.0
Date: Thu, 02 Mar 2017 13:08:13 +0100 [thread overview]
Message-ID: <1488456493.7785.229.camel@intel.com> (raw)
In-Reply-To: <20170302095908.l5n4l4nwjgpih5f4@piout.net>
On Thu, 2017-03-02 at 10:59 +0100, Alexandre Belloni wrote:
> Hi,
>
> On 04/01/2017 at 19:28:46 +0000, Mike Crowe wrote:
> > Upstream has started using automake which means that the recipe must now
> > inherit from autotools and pkgconfig.
> >
> > The source tree has been reorganised too which requires the paths in the
> > patches to be modified. None of the patches appear to have been applied
> > upstream.
> >
>
> They haven't been applied because they have never been submitted
> upstream (despite being tagged with "Upstream-Status: Pending")
That's the problem with "Pending" - it doesn't really mean that the
original author has specific plans in place to get the patches upstream,
and because there's no systematic tracking of "Pending" patches there's
also no pressure to do so once the patch has been accepted into OE-core.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
prev parent reply other threads:[~2017-03-02 12:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 19:28 [PATCH] mtd-utils: Upgrade to 2.0.0 Mike Crowe
2017-03-02 9:59 ` Alexandre Belloni
2017-03-02 12:08 ` Patrick Ohly [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=1488456493.7785.229.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=mac@mcrowe.com \
--cc=openembedded-core@lists.openembedded.org \
/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