Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
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 12:31:43 +0100	[thread overview]
Message-ID: <1304595103.20791.21.camel@rex> (raw)
In-Reply-To: <BANLkTik0nb-ZsqLCnAoXzRr6BLKBUk3cew@mail.gmail.com>

On Wed, 2011-05-04 at 11:39 -0400, Bruce Ashfield wrote:
> On Wed, May 4, 2011 at 10:05 AM, Yu Ke <ke.yu@intel.com> 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
> >
> >  meta-demoapps/recipes-gnome/abiword/abiword_cvs.bb |    1 +
> >  .../recipes-graphics/clutter/table_git.bb          |    1 +
> >  meta-demoapps/recipes-graphics/clutter/tidy_git.bb |    1 +
> 
> <snip>
> 
> >  meta/recipes-kernel/blktrace/blktrace_git.bb       |    2 +
> >  meta/recipes-kernel/dtc/dtc_git.inc                |    2 +
> >  .../kern-tools/kern-tools-native_git.bb            |    1 +
> >  .../linux-firmware/linux-firmware_git.bb           |    1 +
> >  .../linux-libc-headers-yocto_git.bb                |    1 +
> >  .../recipes-kernel/linux/linux-yocto-stable_git.bb |   12 ++
> >  meta/recipes-kernel/linux/linux-yocto_git.bb       |   14 ++\
> 
> Would it be possible to get direct cc on changes to the linux-yocto
> recipes ? I didn't expect this and it is causing me a bit of pain at
> the moment. A direct cc' would have helped, since I would have
> preferred to stage the change in with my other items.

Sorry about that. Hopefully everyone agrees the end result is worth it
though as we're rid of that central file finally :)

Cheers,

Richard




  parent reply	other threads:[~2011-05-05 11:34 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
2011-05-04 15:39 ` Bruce Ashfield
2011-05-05  1:44   ` Yu Ke
2011-05-05 11:31   ` Richard Purdie [this message]
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=1304595103.20791.21.camel@rex \
    --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