From: Alexander Turenko <alexander.turenko@tarantool.org>
To: Konstantin Osipov <kostja@tarantool.org>,
Kirill Yukhin <kyukhin@tarantool.org>
Cc: Alexander Turenko <alexander.turenko@tarantool.org>,
tarantool-patches@freelists.org
Subject: [tarantool-patches] [PATCH 0/2] Travis CI: add Ubuntu Bionic
Date: Thu, 7 Jun 2018 16:43:37 +0300 [thread overview]
Message-ID: <cover.1528374780.git.alexander.turenko@tarantool.org> (raw)
Enable Ubuntu Bionic and support recent debhelper. Related links are in
the commit messages.
This branch supersedes PR #3391.
issue: no
branch: Totktonada/add-ubuntu-bionic
travis-ci: https://travis-ci.org/tarantool/tarantool/builds/389214002
Alexander Turenko (1):
Fix debian package build with recent debhelper
lifemaker (1):
Travis CI: add Ubuntu Bionic
.travis.yml | 4 ++++
debian/rules | 4 ++--
2 files changed, 6 insertions(+), 2 deletions(-)
--
2.17.1
next reply other threads:[~2018-06-07 13:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 13:43 Alexander Turenko [this message]
2018-06-07 13:43 ` [tarantool-patches] [PATCH 1/2] " Alexander Turenko
2018-06-07 13:43 ` [tarantool-patches] [PATCH 2/2] Fix debian package build with recent debhelper Alexander Turenko
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=cover.1528374780.git.alexander.turenko@tarantool.org \
--to=alexander.turenko@tarantool.org \
--cc=kostja@tarantool.org \
--cc=kyukhin@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='Re: [tarantool-patches] [PATCH 0/2] Travis CI: add Ubuntu Bionic' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox