From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 12c244b3e9d4c31d0703813b0986d06b18124377
Date: Fri, 23 Nov 2012 01:40:30 +0100 [thread overview]
Message-ID: <20121123004031.0F01D202AF@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1465 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 12c244b3e9d4c31d0703813b0986d06b18124377 (commit)
from 5af29fb326ea1abbbb166a3ffba713a1aebaf126 (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 12c244b3e9d4c31d0703813b0986d06b18124377
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Fri Nov 23 01:40:01 2012 +0100
tinc: Update to 1.0.19.
-----------------------------------------------------------------------
Summary of changes:
tinc/tinc.nm | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
Difference in files:
diff --git a/tinc/tinc.nm b/tinc/tinc.nm
index 1bf179b..48eb0e4 100644
--- a/tinc/tinc.nm
+++ b/tinc/tinc.nm
@@ -4,7 +4,7 @@
###############################################################################
name = tinc
-version = 1.0.14
+version = 1.0.19
release = 1
groups = Networking/Tools
@@ -34,7 +34,6 @@ end
packages
package %{name}
- end
package %{name}-debuginfo
template DEBUGINFO
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2012-11-23 0:40 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=20121123004031.0F01D202AF@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