From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. cadcad57788eaa48548e23b96925ef295226652d
Date: Wed, 16 Mar 2016 22:37:35 +0000 [thread overview]
Message-ID: <20160316223736.2E8BF1081BC7@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1709 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 cadcad57788eaa48548e23b96925ef295226652d (commit)
from 85737c42289bec99e10c8c2802ccd2d5c8b4e875 (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 cadcad57788eaa48548e23b96925ef295226652d
Author: Alexander Marx <alexander.marx(a)ipfire.org>
Date: Wed Mar 16 14:36:23 2016 +0100
tzdata: Update to version 2016b
This is a Bug-fix release
Fixes: #11032, #11063
Signed-off-by: Alexander Marx <alexander.marx(a)ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
tzdata/tzdata.nm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/tzdata/tzdata.nm b/tzdata/tzdata.nm
index c1554c1..0482afc 100644
--- a/tzdata/tzdata.nm
+++ b/tzdata/tzdata.nm
@@ -3,8 +3,8 @@
# Copyright (C) - IPFire Development Team <info(a)ipfire.org> #
###############################################################################
-tzdata_version = 2015g
-tzcode_version = 2015g
+tzdata_version = 2016b
+tzcode_version = 2016b
name = tzdata
version = %{tzdata_version}
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2016-03-16 22:37 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=20160316223736.2E8BF1081BC7@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