From: Tomas Frydrych <tf+lists.yocto@r-finger.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/5] Enable VPN support in ConnMan
Date: Mon, 13 May 2013 12:32:51 +0100 [thread overview]
Message-ID: <5190CF63.2030303@r-finger.com> (raw)
In-Reply-To: <CAJTo0LYSqikcyXKsXA5OpnUNmwbvrRqbi4kQ93r2QzBtEuo2zQ@mail.gmail.com>
On 13/05/13 12:06, Burton, Ross wrote:
> The problem with bbappends is that they break every time the package
> in oe-core changes version.
I see this as a good thing; if I maintain a bbappend, I want to know
when the base package changes its a version, and I get an immediate
error due to bbappend to a non-existent file.
Tomas
--
http://sleepfive.com
next prev parent reply other threads:[~2013-05-13 11:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 12:33 [PATCH 0/5] Enable VPN support in ConnMan Jukka Rissanen
2013-05-10 12:33 ` [PATCH 1/5] connman: Enable VPN support Jukka Rissanen
2013-05-10 12:33 ` [PATCH 2/5] connman: Add OpenVPN support Jukka Rissanen
2013-05-10 12:33 ` [PATCH 3/5] connman: Add vpnc support Jukka Rissanen
2013-05-10 12:33 ` [PATCH 4/5] connman: Add L2TP support Jukka Rissanen
2013-05-10 12:33 ` [PATCH 5/5] connman: Add PPTP support Jukka Rissanen
2013-05-10 13:47 ` [PATCH 0/5] Enable VPN support in ConnMan Burton, Ross
2013-05-10 22:22 ` Saul Wold
2013-05-11 13:59 ` Philip Balister
2013-05-12 13:27 ` Otavio Salvador
2013-05-12 15:40 ` Saul Wold
2013-05-12 16:32 ` Khem Raj
2013-05-12 18:54 ` Phil Blundell
2013-05-12 19:55 ` Paul Eggleton
2013-05-13 8:00 ` Saul Wold
2013-05-13 8:33 ` Paul Eggleton
2013-05-13 8:44 ` Saul Wold
2013-05-13 11:02 ` Phil Blundell
2013-05-13 11:06 ` Burton, Ross
2013-05-13 11:16 ` Phil Blundell
2013-05-13 11:32 ` Tomas Frydrych [this message]
2013-05-13 14:24 ` Burton, Ross
2013-05-13 14:53 ` Phil Blundell
2013-05-14 9:22 ` Tomas Frydrych
2013-05-14 10:18 ` Richard Purdie
2013-05-15 21:25 ` Phil Blundell
2013-05-14 12:30 ` libsoup missing DEPENDS Mike Looijmans
2013-05-14 12:36 ` Burton, Ross
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=5190CF63.2030303@r-finger.com \
--to=tf+lists.yocto@r-finger.com \
--cc=openembedded-core@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