From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next 1/1] package/git-crypt: bump version to 0.6.0
Date: Mon, 20 Aug 2018 14:35:33 +0200 [thread overview]
Message-ID: <20180820143533.3f651705@windsurf> (raw)
In-Reply-To: <20180819071821.17780-1-bernd.kuhls@t-online.de>
Hello,
On Sun, 19 Aug 2018 09:18:21 +0200, Bernd Kuhls wrote:
> Quoting from release notes:
> https://www.agwa.name/git/git-crypt.git/raw/master/NEWS
>
> "v0.6.0 (2017-11-26)
> * Add support for OpenSSL 1.1 (still works with OpenSSL 1.0).
> * Switch to C++11 (gcc 4.9 or higher now required to build).
> [...]"
>
> Added license hashes.
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> package/git-crypt/Config.in | 6 ++++--
> package/git-crypt/git-crypt.hash | 7 +++++--
> package/git-crypt/git-crypt.mk | 2 +-
> 3 files changed, 10 insertions(+), 5 deletions(-)
Applied to next, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-08-20 12:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-19 7:18 [Buildroot] [PATCH/next 1/1] package/git-crypt: bump version to 0.6.0 Bernd Kuhls
2018-08-20 12:35 ` Thomas Petazzoni [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=20180820143533.3f651705@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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