From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-systemd][PATCH] connman: Rename .bbappend to match new version from oe-core
Date: Wed, 29 Jan 2014 08:55:50 +0100 [thread overview]
Message-ID: <lcac4m$c5i$2@ger.gmane.org> (raw)
In-Reply-To: <1390943894-18907-1-git-send-email-Martin.Jansa@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Martin Jansa schreef op 28-01-14 22:18:
> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> ---
> .../connman/{connman_1.20.bbappend => connman_%.bbappend}
> | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename
> meta-systemd/oe-core/recipes-connectivity/connman/{connman_1.20.bbappend
> => connman_%.bbappend} (100%)
>
> diff --git
> a/meta-systemd/oe-core/recipes-connectivity/connman/connman_1.20.bbappend
> b/meta-systemd/oe-core/recipes-connectivity/connman/connman_%.bbappend
> similarity index 100% rename from
> meta-systemd/oe-core/recipes-connectivity/connman/connman_1.20.bbappend
> rename to
> meta-systemd/oe-core/recipes-connectivity/connman/connman_%.bbappend
Can we come up with a plan to drop these packaging bbappends? We've already
had more than one OE (well yoctoproject) release so distros have had ample
time to adjust to the new packaging system.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org
iD8DBQFS6LQGMkyGM64RGpERAuYSAJ9s0a8ZiO46TgHYEeU847dYSbJ0fgCeM7ZY
ksC7lfMtsOUETerxdMBX3h8=
=x7iV
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-01-29 8:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 21:18 [meta-systemd][PATCH] connman: Rename .bbappend to match new version from oe-core Martin Jansa
2014-01-29 7:55 ` Koen Kooi [this message]
2014-01-29 10:15 ` Martin Jansa
2014-01-29 10:41 ` Koen Kooi
-- strict thread matches above, loose matches on Subject: below --
2013-03-07 15:53 [meta-systemd][PATCH] connman: rename " Martin Jansa
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='lcac4m$c5i$2@ger.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.