From: Yu Ke <ke.yu@intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] poky-default-revisions: move SRCREV to every recipe
Date: Thu, 05 May 2011 08:50:18 +0800 [thread overview]
Message-ID: <4DC1F44A.3020708@intel.com> (raw)
In-Reply-To: <BANLkTinduv4VofN2=adDN2-HZozYTO45ew@mail.gmail.com>
on 2011-5-4 22:24, Frans Meulenbroeks wrote:
> 2011/5/4 Richard Purdie<richard.purdie@linuxfoundation.org>
>
>> On Wed, 2011-05-04 at 22:05 +0800, Yu Ke wrote:
>>> From: Yu Ke<ke.yu@intel.com>
>>>
>>> move the SRCREV from poky-default-revisions.inc to its corresponding
>> recipe,
>>> in this case, those non poky distro can also use its SRCREV.
>>>
>>> Pull URL: git://git.pokylinux.org/poky-contrib.git
>>> Branch: kyu3/srcrev-recipe
>>> Browse:
>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=kyu3/srcrev-recipe
>>>
>>> Thanks,
>>> Yu Ke<ke.yu@intel.com>
>>> ---
>>>
>>>
>>> Yu Ke (1):
>>> poky-default-revisions: move the SRCREV to recipe file
>>
>> Merged to master, thanks for resolving this issue! :)
>>
>> Cheers,
>>
>> Richard
>>
>> I would have preferred a more standardised placement of SRCREV.
> Most of the time the SRCREV is before the PV, but not always (and sometimes
> separated with an empty line and sometimes not).
>
> Also there is at least one error introduced:
>
> diff --git a/meta/recipes-devtools/yaffs2/yaffs2-utils_cvs.bbb/meta/recipes-devtools/yaffs2/
> yaffs2-utils_cvs.bb
> index 6171fe5..c729c7c 100644
> --- a/meta/recipes-devtools/yaffs2/yaffs2-utils_cvs.bb<http://git.pokylinux.org/cgit.cgi/poky-contrib/tree/meta/recipes-devtools/yaffs2/yaffs2-utils_cvs.bb?h=kyu3/srcrev-recipe&id=d2e078aa046ae6c4f169695f546cf229db5be1f7>
> +++ b/meta/recipes-devtools/yaffs2/yaffs2-utils_cvs.bb<http://git.pokylinux.org/cgit.cgi/poky-contrib/tree/meta/recipes-devtools/yaffs2/yaffs2-utils_cvs.bb?h=kyu3/srcrev-recipe&id=c75b49ff5cfd10f5187af2b66a0a8d5513460374>
> @@ -1,3 +1,4 @@
> require yaffs2-utils.inc
> PR = "r1"
> +SRCDAT = "20071107"
>
> That should be SRCDATE. There might be more of these, my eye just fell on
> this one.
Thanks for pointing it out. For unknown reason, my proxy does not work
in cvs fetcher , so this recipe is untested. I should take more care on
this. A patch is just sent out to fix it.
Regards
Ke
>
> Frans
>
> PS: speaking of yaffs2 utils: it could be considered to move to a somewhat
> newer version (not that I care as I do not use yaffs2)
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2011-05-05 0:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 14:05 [PATCH 0/1] poky-default-revisions: move SRCREV to every recipe Yu Ke
2011-05-04 14:05 ` [PATCH 1/1] poky-default-revisions: move the SRCREV to recipe file Yu Ke
2011-05-04 14:07 ` [PATCH 0/1] poky-default-revisions: move SRCREV to every recipe Richard Purdie
2011-05-04 14:24 ` Frans Meulenbroeks
2011-05-04 16:00 ` Richard Purdie
2011-05-04 17:10 ` Frans Meulenbroeks
2011-05-05 0:50 ` Yu Ke [this message]
2011-05-04 15:39 ` Bruce Ashfield
2011-05-05 1:44 ` Yu Ke
2011-05-05 11:31 ` Richard Purdie
2011-05-05 12:45 ` Bruce Ashfield
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=4DC1F44A.3020708@intel.com \
--to=ke.yu@intel.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