From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. ad134621260cee8bc62a0df09b288a96b694be85
Date: Thu, 20 Sep 2012 20:12:06 +0200 [thread overview]
Message-ID: <20120920181207.476D620099@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1656 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 ad134621260cee8bc62a0df09b288a96b694be85 (commit)
via 9df4923ff12e7b131e0ff389ab296e4d3b8c9e7a (commit)
from 577ebde09079ed794c3af4b9c718cf80540dd033 (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 ad134621260cee8bc62a0df09b288a96b694be85
Merge: 577ebde 9df4923
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Sep 20 20:11:59 2012 +0200
Merge remote-tracking branch 'ms/gcc-update'
commit 9df4923ff12e7b131e0ff389ab296e4d3b8c9e7a
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Sep 20 17:06:09 2012 +0000
gcc: Update to 4.7.2.
This is the second bugfix release of the GCC 4.7 series.
-----------------------------------------------------------------------
Summary of changes:
gcc/gcc.nm | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/gcc/gcc.nm b/gcc/gcc.nm
index 69f6fd2..2723547 100644
--- a/gcc/gcc.nm
+++ b/gcc/gcc.nm
@@ -7,8 +7,8 @@
build_cloog_ppl = 1
name = gcc
-version = 4.7.1
-release = 3
+version = 4.7.2
+release = 1
maintainer = Michael Tremer <michael.tremer(a)ipfire.org>
groups = Development/Compilers
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2012-09-20 18:12 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=20120920181207.476D620099@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