From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] python: Fix re-execution problem due to patching configure and configure.in
Date: Mon, 16 Apr 2012 12:10:53 +0100 [thread overview]
Message-ID: <1334574653.16992.74.camel@ted> (raw)
In-Reply-To: <111FD132-7323-472B-8052-283E454DCB6E@dominion.thruhere.net>
On Mon, 2012-04-16 at 12:50 +0200, Koen Kooi wrote:
> Op 16 apr. 2012, om 11:47 heeft Richard Purdie het volgende geschreven:
>
> > There was a patch patching both configure and configure.in. Since the recipes
> > all autoreconf, this is pointless and means subsequent patch tasks fail.
> >
> > The fix is to only patch configure.in.
> >
> > [YOCTO #2194]
> >
> > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
>
> Since this changes the sources it needs a PR bump.
It has no effect on the packaged output which was always the criteria
for PR bumps as I understood things.
Cheers,
Richard
next prev parent reply other threads:[~2012-04-16 11:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 9:47 [PATCH] python: Fix re-execution problem due to patching configure and configure.in Richard Purdie
2012-04-16 10:50 ` Koen Kooi
2012-04-16 11:10 ` Richard Purdie [this message]
2012-04-16 11:27 ` Koen Kooi
2012-04-16 15:31 ` Steve Sakoman
2012-04-16 15:51 ` Richard Purdie
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=1334574653.16992.74.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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