From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core105, created. 8bbed7a5b6a878dae03d605042b48304f3900304
Date: Thu, 22 Sep 2016 10:41:53 +0100 [thread overview]
Message-ID: <20160922094154.559011078E81@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1479 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 2.x development tree".
The branch, core105 has been created
at 8bbed7a5b6a878dae03d605042b48304f3900304 (commit)
- Log -----------------------------------------------------------------
commit 8bbed7a5b6a878dae03d605042b48304f3900304
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Sep 22 10:30:28 2016 +0100
core105: Ship security update for libgcrypt
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
commit db7ef87902096d8268bb348ba5821eba344e27ba
Author: Matthias Fischer <matthias.fischer(a)ipfire.org>
Date: Sat Aug 20 12:33:55 2016 +0200
libgcrypt: Update to 1.7.3
Fixes CVE-2016-6313
For details, see:
https://lists.gnupg.org/pipermail/gnupg-announce/2016q3/000395.html
https://bugzilla.redhat.com/show_bug.cgi?id=1366105
Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
commit c4a1169ed975c15ee8c29c99d0667388a09c29bf
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Sep 22 10:28:36 2016 +0100
Start Core Update 105
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2016-09-22 9:41 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=20160922094154.559011078E81@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