From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [IPFire-SCM] [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 309682b01fe96f564ba3270f07bd688a9a91ebcc
Date: Thu, 07 Jun 2012 15:26:22 +0200 [thread overview]
Message-ID: <20120607132623.33ECB20166@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1452 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 309682b01fe96f564ba3270f07bd688a9a91ebcc (commit)
from 0111cbc98d5626c49829149a2a923706adda9163 (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 309682b01fe96f564ba3270f07bd688a9a91ebcc
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Jun 7 15:25:59 2012 +0200
bison: Update to 2.5.1.
Fixes #10146.
-----------------------------------------------------------------------
Summary of changes:
bison/bison.nm | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/bison/bison.nm b/bison/bison.nm
index 6b8bcc5..1313285 100644
--- a/bison/bison.nm
+++ b/bison/bison.nm
@@ -4,8 +4,8 @@
###############################################################################
name = bison
-version = 2.5
-release = 3
+version = 2.5.1
+release = 1
groups = Development/Tools
url = http://www.gnu.org/software/bison/
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2012-06-07 13:26 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=20120607132623.33ECB20166@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