From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Constantin Musca <constantinx.musca@intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] libxslt: upgrade to 1.1.27
Date: Mon, 12 Nov 2012 12:55:41 +0000 [thread overview]
Message-ID: <1352724941.9083.32.camel@ted> (raw)
In-Reply-To: <CAJTo0LZE56zn8UeSZ8OHs_oCX2U+y=L+F+HD9Dm74JPZyp_Eow@mail.gmail.com>
On Fri, 2012-11-09 at 10:15 +0000, Burton, Ross wrote:
> On 9 November 2012 10:00, Constantin Musca <constantinx.musca@intel.com> wrote:
> > --- a/meta/recipes-support/libxslt/libxslt/pkgconfig_fix.patch
> > +++ b/meta/recipes-support/libxslt/libxslt/pkgconfig_fix.patch
> > @@ -1,24 +1,24 @@
> > Upstream-Status: Inappropriate [configuration]
>
> This doesn't look "inappropriate" or "configuration" but a genuine
> build fix. Has anyone approached upstream?
>
> (I'm genuinely dismayed at the number of build fixes that get marked
> as inappropriate when they are clearly genuine build fixes)
I'm not going to reject the patch on this since its not a new issue
being introduced but I do support what you're saying 100% here, the
categories do seem to have gotten a little misplaced and people should
take the time to validate them when upgrading recipes...
Cheers,
Richard
prev parent reply other threads:[~2012-11-12 13:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 10:00 [PATCH 1/2] libxslt: upgrade to 1.1.27 Constantin Musca
2012-11-09 10:00 ` [PATCH 2/2] puzzles: upgrade to r9660 Constantin Musca
2012-11-09 10:15 ` [PATCH 1/2] libxslt: upgrade to 1.1.27 Burton, Ross
2012-11-12 12:55 ` Richard Purdie [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=1352724941.9083.32.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=constantinx.musca@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@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 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.