From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Andrew Bradford <andrew@bradfordembedded.com>,
openembedded-core@lists.openembedded.org
Cc: Andrew Bradford <andrew.bradford@kodakalaris.com>
Subject: Re: [PATCH 3/3] base.bbclass: p4 fetcher supports srcrev
Date: Fri, 17 Jun 2016 17:08:20 +0100 [thread overview]
Message-ID: <1466179700.25557.15.camel@linuxfoundation.org> (raw)
In-Reply-To: <20160617125230.GA9776@kaim-eeyore.kodakalaris.net>
On Fri, 2016-06-17 at 08:52 -0400, Andrew Bradford wrote:
> On 05/25 15:46, Andrew Bradford wrote:
> I noticed that this patch has not been applied to oe-core, but it is
> a
> dependency for the bitbake perforce fetcher change to support srcrev
> which has been applied to bitbake's master branch [1].
>
> [1]:http://git.openembedded.org/bitbake/commit/?id=6298696bb94a127cde
> c7964315f6891ba92cd026
>
> Any chance that this patch could be applied to oe-core?
> The other two patches in this series are not needed, just this one.
> Sorry if my bitbake patch was not super clear about this dependency.
Normally patches land in bitbake first, then the code which uses them
goes into OE-Core and we bump the minimum bitbake version. In this case
I doubt we need the version bump as p4 isn't widely used.
I've merged the patch, thanks for the reminder we need that one.
Cheers,
Richard
next prev parent reply other threads:[~2016-06-17 16:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 19:46 [PATCH 0/3] Setup for bitbake perforce fetcher changes Andrew Bradford
2016-05-25 19:46 ` [PATCH 1/3] oe-buildenv-internal: Add P4CONFIG to BB_ENV_EXTRAWHITE_OE Andrew Bradford
2016-06-02 15:53 ` Richard Purdie
2016-05-25 19:46 ` [PATCH 2/3] bitbake.conf: Add P4DIR and FETCHCMD_p4 Andrew Bradford
2016-06-02 15:56 ` Richard Purdie
2016-06-02 17:06 ` Andrew Bradford
2016-05-25 19:46 ` [PATCH 3/3] base.bbclass: p4 fetcher supports srcrev Andrew Bradford
2016-06-17 12:52 ` Andrew Bradford
2016-06-17 16:08 ` Richard Purdie [this message]
2016-06-02 13:41 ` [PATCH 0/3] Setup for bitbake perforce fetcher changes Andrew Bradford
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=1466179700.25557.15.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=andrew.bradford@kodakalaris.com \
--cc=andrew@bradfordembedded.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 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.