From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Cc: openembedded-devel@lists.openembedded.org,
yocto <yocto@yoctoproject.org>
Subject: Re: New OE layer index now available
Date: Thu, 04 Apr 2013 16:23 +0100 [thread overview]
Message-ID: <4508990.pcm6NvoxmA@helios> (raw)
In-Reply-To: <CAOT3miKi62MtFGjiNYeykNKAsFQ+srtwqSbsSyge3ZzGHD4DOw@mail.gmail.com>
On Thursday 04 April 2013 17:01:07 Nicolas Dechesne wrote:
> i was thinking it might be useful (in fact at least it would be very
> useful for me right now) to get version 'history' for each supported
> branch. if i understand the design correctly, i first need to set the
> branch I want to search, then search. but what about an 'all branch
> search' that displays recipes version *and* layer for multiple
> branches, so that we can easily see version change and recipe move
> in-between layers between all branches.
Hmm, I hadn't thought of that, but yes it does sound useful. I'll add it to
the todo list.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
WARNING: multiple messages have this Message-ID (diff)
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Cc: Nicolas Dechesne <ndec13@gmail.com>,
openembedded-devel@lists.openembedded.org,
yocto <yocto@yoctoproject.org>
Subject: Re: [OE-core] New OE layer index now available
Date: Thu, 04 Apr 2013 16:23 +0100 [thread overview]
Message-ID: <4508990.pcm6NvoxmA@helios> (raw)
In-Reply-To: <CAOT3miKi62MtFGjiNYeykNKAsFQ+srtwqSbsSyge3ZzGHD4DOw@mail.gmail.com>
On Thursday 04 April 2013 17:01:07 Nicolas Dechesne wrote:
> i was thinking it might be useful (in fact at least it would be very
> useful for me right now) to get version 'history' for each supported
> branch. if i understand the design correctly, i first need to set the
> branch I want to search, then search. but what about an 'all branch
> search' that displays recipes version *and* layer for multiple
> branches, so that we can easily see version change and recipe move
> in-between layers between all branches.
Hmm, I hadn't thought of that, but yes it does sound useful. I'll add it to
the todo list.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
WARNING: multiple messages have this Message-ID (diff)
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Cc: openembedded-devel@lists.openembedded.org,
yocto <yocto@yoctoproject.org>
Subject: Re: [OE-core] New OE layer index now available
Date: Thu, 04 Apr 2013 16:23 +0100 [thread overview]
Message-ID: <4508990.pcm6NvoxmA@helios> (raw)
In-Reply-To: <CAOT3miKi62MtFGjiNYeykNKAsFQ+srtwqSbsSyge3ZzGHD4DOw@mail.gmail.com>
On Thursday 04 April 2013 17:01:07 Nicolas Dechesne wrote:
> i was thinking it might be useful (in fact at least it would be very
> useful for me right now) to get version 'history' for each supported
> branch. if i understand the design correctly, i first need to set the
> branch I want to search, then search. but what about an 'all branch
> search' that displays recipes version *and* layer for multiple
> branches, so that we can easily see version change and recipe move
> in-between layers between all branches.
Hmm, I hadn't thought of that, but yes it does sound useful. I'll add it to
the todo list.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-04-04 15:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 21:34 New OE layer index now available Paul Eggleton
2013-03-29 21:58 ` Otavio Salvador
2013-03-29 21:58 ` [OE-core] " Otavio Salvador
2013-03-29 22:07 ` Paul Eggleton
2013-03-29 22:07 ` [OE-core] " Paul Eggleton
2013-04-01 10:47 ` Joe MacDonald
2013-04-01 11:57 ` Paul Eggleton
2013-04-01 11:57 ` [OE-core] " Paul Eggleton
2013-04-01 13:06 ` Joe MacDonald
2013-04-04 15:01 ` Nicolas Dechesne
2013-04-04 15:01 ` [OE-core] " Nicolas Dechesne
2013-04-04 15:23 ` Paul Eggleton [this message]
2013-04-04 15:23 ` Paul Eggleton
2013-04-04 15:23 ` Paul Eggleton
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=4508990.pcm6NvoxmA@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=yocto@yoctoproject.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.