From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-meta 0/2] pull request: vim, wget
Date: Tue, 19 Apr 2011 13:42:20 +0200 [thread overview]
Message-ID: <iojses$p5q$1@dough.gmane.org> (raw)
In-Reply-To: <BANLkTi=Qxc2p2FMrTuA_UcRbGEm0rkUSbA@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 19-04-11 11:42, Michael Lippautz wrote:
> 2011/4/19 Koen Kooi <koen@dominion.thruhere.net>:
> On 18-04-11 21:32, Michael Lippautz wrote:
>>>> Re-import of vim/gvim/vim-tiny and wget.
>>>>
>>>> * Clean vim recipe and update to 7.2.446 (446=patchset)
>>>> * Clean wget (ssl check using staging_dir)
>>>>
>>>> Pull URL: git://gitorious.org/oe-zoid/meta-openembedded.git
>>>> Branch: master
>>>> Browse: http://gitorious.org/oe-zoid/meta-openembedded/commits/master
>
> merged, thanks
>
>> Thanks for correcting the space escape ...
>
>> I also didn't know that meta-oe doesn't care about distro overrides anymore.
All distro overrides should be done in their respective layer (e.g.
meta-angstrom, meta-shr). Just like machine overrides should be done in
their respective layers.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFNrXUcMkyGM64RGpERAgwzAJ4yuuPnc2hhGLDYYdsxFdDs4tlpfQCffBj+
Ly1EwHhJQovVAvb0yIiG9a0=
=PE5X
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2011-04-19 11:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 19:32 [oe-meta 0/2] pull request: vim, wget Michael Lippautz
2011-04-18 19:32 ` [oe-meta 1/2] wget: Add version 1.11.4 Michael Lippautz
2011-04-18 19:32 ` [oe-meta 2/2] vim: Add vim/tiny-vim/gvim 7.2 (patchset 446) Michael Lippautz
2011-04-18 19:45 ` [oe-meta 0/2] pull request: vim, wget Paul Menzel
2011-04-19 9:24 ` Koen Kooi
2011-04-19 9:42 ` Michael Lippautz
2011-04-19 11:42 ` Koen Kooi [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='iojses$p5q$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 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.