From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 8adf51b8ca1ca82565af02579f470a472fa6c27f
Date: Wed, 31 Jul 2013 00:44:18 +0200 [thread overview]
Message-ID: <20130730224419.5E2D22075C@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1420 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 8adf51b8ca1ca82565af02579f470a472fa6c27f (commit)
from 9880404af7dae451223ccbb6d961dc09f8f02947 (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 8adf51b8ca1ca82565af02579f470a472fa6c27f
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Wed Jul 31 00:40:15 2013 +0200
gnupg2: Update to 2.0.20.
-----------------------------------------------------------------------
Summary of changes:
gnupg2/gnupg2.nm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/gnupg2/gnupg2.nm b/gnupg2/gnupg2.nm
index ff5a93a..5ea39ae 100644
--- a/gnupg2/gnupg2.nm
+++ b/gnupg2/gnupg2.nm
@@ -4,8 +4,8 @@
###############################################################################
name = gnupg2
-version = 2.0.18
-release = 2
+version = 2.0.20
+release = 1
thisapp = gnupg-%{version}
groups = Security/Tools
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2013-07-30 22:44 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=20130730224419.5E2D22075C@argus.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