From: Saul Wold <sgw@linux.intel.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] Update proto -> protocol for recipes
Date: Thu, 12 Jul 2012 10:49:01 -0700 [thread overview]
Message-ID: <4FFF0E0D.3060304@linux.intel.com> (raw)
In-Reply-To: <1719877.VOngMK1fKZ@helios>
On 07/12/2012 10:41 AM, Paul Eggleton wrote:
> On Thursday 12 July 2012 10:35:02 Saul Wold wrote:
>> Signed-off-by: Saul Wold <sgw@linux.intel.com>
>> ---
>> meta/recipes-core/eglibc/eglibc_2.15.bb | 2 +-
>> meta/recipes-devtools/gcc/gcc-4.7.inc | 2 +-
>> .../installer/adt-installer_1.0.bb | 2 +-
>> meta/recipes-devtools/opkg/opkg_svn.bb | 2 +-
>> meta/recipes-devtools/tcf-agent/tcf-agent_git.bb | 2 +-
>> meta/recipes-devtools/ubootchart/ubootchart_svn.bb | 2 +-
>> meta/recipes-gnome/gtkhtml2/gtkhtml2_svn.bb | 2 +-
>> .../matchbox-wm-2/matchbox-wm-2_git.bb | 2 +-
>> meta/recipes-sato/webkit/webkit-gtk_svn.bb | 6 +++---
>> 9 files changed, 11 insertions(+), 11 deletions(-)
>
> I don't think we can do this for the svn recipes until the minimum
> bitbake version has been bumped, since older bitbake versions won't
> support the "protocol" parameter. For git, I'm not sure 'proto' has
> ever been valid at least for fetch2.
>
Yes, you are correct, we need to wait for the bitbake rev to occur,
should have thought about that. I was using the lastest version in poky
which also complained about the git proto, so they where just being
ignored in the past.
Sau!
> Cheers,
> Paul
>
prev parent reply other threads:[~2012-07-12 18:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 17:35 [PATCH] Update proto -> protocol for recipes Saul Wold
2012-07-12 17:41 ` Paul Eggleton
2012-07-12 17:49 ` Saul Wold [this message]
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=4FFF0E0D.3060304@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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