From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][meta-efl][PATCH] various: update ; proto= to ; protocol= in SRC_URI
Date: Sun, 15 Jul 2012 12:32:25 +0200 [thread overview]
Message-ID: <jtu67p$oft$1@dough.gmane.org> (raw)
In-Reply-To: <1545322.vi2fespzus@helios>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 13-07-12 17:40, Paul Eggleton schreef:
> On Friday 13 July 2012 17:37:47 Koen Kooi wrote:
>> Op 13 jul. 2012, om 17:35 heeft Paul Eggleton het volgende geschreven:
>>> On Friday 13 July 2012 17:26:45 Koen Kooi wrote:
>>>> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
>>>
>>> Just checking, you're aware that for the svn fetcher this will break
>>> with older versions of bitbake that don't have the recent patch
>>> applied?
>>>
>>> If that's not a concern, no problem.
>>
>> Not a concern for meta-oe master, only for release branches :)
>
> My thinking was that at least in the OE-Classic days we didn't expect the
> user to have bleeding edge bitbake even in master.
OE-core changed all that :/ I know RP avoids hard dependencies, but to avoid
"that was fixed in bitbake master last week" type of responses the angstrom
scripts that track oe-core master also track bitbake master.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org
iD8DBQFQApw5MkyGM64RGpERAuCnAKCB6B5X4jcmHpbFnbRFfvzw9wZ+OgCeMZzc
+KDiQv7qTysxp+Ryoj3Q2EM=
=pbrL
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-07-15 10:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 15:26 [meta-oe][meta-efl][PATCH] various: update ; proto= to ; protocol= in SRC_URI Koen Kooi
2012-07-13 15:35 ` Paul Eggleton
2012-07-13 15:37 ` Koen Kooi
2012-07-13 15:40 ` Paul Eggleton
2012-07-15 10:32 ` Koen Kooi [this message]
2012-07-16 8:47 ` Martin Jansa
2012-07-16 9:07 ` Koen Kooi
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='jtu67p$oft$1@dough.gmane.org' \
--to=koen@dominion.thruhere.net \
--cc=openembedded-devel@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