From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Armin Kuster <akuster808@gmail.com>,
openembedded-devel@lists.openembedded.org
Subject: [meta-oe][PATCH v2 0/4] libgpiod: support for v1.0 series
Date: Tue, 17 Apr 2018 16:20:16 +0200 [thread overview]
Message-ID: <20180417142020.30100-1-brgl@bgdev.pl> (raw)
I recently released a new major version of libgpiod in which the
initial API was heavily reworked. Since it's no longer compatible
with v0.3.3 but I know there are users of the latter and I also
intend on supporting it for some time, I thought we should have both
versions in recipes-support.
This series adds a new recipe for libgpiod v1.0.1 that can live next to
v0.3.3.
v1 -> v2:
- there was no reply to the previous series, and new v0.3.x and v1.0.x
versions have been released during that time, so v2 bumps the versions
Bartosz Golaszewski (4):
libgpiod: include the version in the recipe filename
libgpiod: split recipe into .inc and .bb files
libgpiod: bump version to v0.3.3
libgpiod: add support for v1.x series
.../recipes-support/libgpiod/{libgpiod.bb => libgpiod.inc} | 5 -----
meta-oe/recipes-support/libgpiod/libgpiod_0.3.3.bb | 4 ++++
meta-oe/recipes-support/libgpiod/libgpiod_1.0.1.bb | 4 ++++
3 files changed, 8 insertions(+), 5 deletions(-)
rename meta-oe/recipes-support/libgpiod/{libgpiod.bb => libgpiod.inc} (80%)
create mode 100644 meta-oe/recipes-support/libgpiod/libgpiod_0.3.3.bb
create mode 100644 meta-oe/recipes-support/libgpiod/libgpiod_1.0.1.bb
--
2.17.0
next reply other threads:[~2018-04-17 14:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 14:20 Bartosz Golaszewski [this message]
2018-04-17 14:20 ` [meta-oe][PATCH v2 1/4] libgpiod: include the version in the recipe filename Bartosz Golaszewski
2018-04-17 14:20 ` [meta-oe][PATCH v2 2/4] libgpiod: split recipe into .inc and .bb files Bartosz Golaszewski
2018-04-17 14:20 ` [meta-oe][PATCH v2 3/4] libgpiod: bump version to v0.3.3 Bartosz Golaszewski
2018-04-17 14:20 ` [meta-oe][PATCH v2 4/4] libgpiod: add support for v1.x series Bartosz Golaszewski
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=20180417142020.30100-1-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--cc=akuster808@gmail.com \
--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