From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 6bb58a239137257ef3eaaf6d1efc0f0b1d34d143
Date: Tue, 28 Jan 2014 22:19:23 +0100 [thread overview]
Message-ID: <20140128211951.8C3BA20C3C@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1591 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 6bb58a239137257ef3eaaf6d1efc0f0b1d34d143 (commit)
from 2c8d4c74e7dc8ca360abf4bc6514c7931e1070b3 (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 6bb58a239137257ef3eaaf6d1efc0f0b1d34d143
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Mon Jan 27 23:41:26 2014 +0100
gawk: Update to 4.1.0.
Adds dependency to MPFR for high precision math.
-----------------------------------------------------------------------
Summary of changes:
gawk/gawk.nm | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/gawk/gawk.nm b/gawk/gawk.nm
index 2b7d077..8c335f3 100644
--- a/gawk/gawk.nm
+++ b/gawk/gawk.nm
@@ -4,8 +4,8 @@
###############################################################################
name = gawk
-version = 4.0.1
-release = 2
+version = 4.1.0
+release = 1
groups = System/Tools
url = http://www.gnu.org/software/gawk/gawk.html
@@ -24,6 +24,7 @@ sources = %{thisapp}.tar.xz
build
requires
+ mpfr-devel
util-linux
end
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2014-01-28 21:19 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=20140128211951.8C3BA20C3C@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