From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 4b05c93e419bb35973b3bbc5a745b0bb38d9ce0d
Date: Fri, 02 Sep 2016 09:04:20 +0100 [thread overview]
Message-ID: <20160902080420.6A9D81078E81@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1638 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 3.x development tree".
The branch, master has been updated
via 4b05c93e419bb35973b3bbc5a745b0bb38d9ce0d (commit)
from 22f8b3bcd86f5afc216d9480fca79db06e0d2bfb (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 4b05c93e419bb35973b3bbc5a745b0bb38d9ce0d
Author: Alexander Marx <alexander.marx(a)ipfire.org>
Date: Mon May 23 13:12:38 2016 +0200
libgcrypt: update to 1.7.0
Fixes: #11100
Changelog
https://bugzilla.ipfire.org/show_bug.cgi?id=11100
Signed-off-by: Alexander Marx <alexander.marx(a)ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
libgcrypt/libgcrypt.nm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/libgcrypt/libgcrypt.nm b/libgcrypt/libgcrypt.nm
index 18f1ae3..10707a1 100644
--- a/libgcrypt/libgcrypt.nm
+++ b/libgcrypt/libgcrypt.nm
@@ -4,7 +4,7 @@
###############################################################################
name = libgcrypt
-version = 1.6.5
+version = 1.7.0
release = 1
groups = System/Libraries
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2016-09-02 8:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160902080420.6A9D81078E81@git01.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.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