From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. bea58a22c10c35e67050fe9811fd295107c453ba
Date: Thu, 30 May 2013 11:29:57 +0200 [thread overview]
Message-ID: <20130530093007.599FE200BE@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1378 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 bea58a22c10c35e67050fe9811fd295107c453ba (commit)
from 145028080647e86f0fa66b66e16161e32f2e612c (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 bea58a22c10c35e67050fe9811fd295107c453ba
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu May 30 11:12:00 2013 +0200
bison: Update to 2.7.1.
Fixes #10356.
-----------------------------------------------------------------------
Summary of changes:
bison/bison.nm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/bison/bison.nm b/bison/bison.nm
index dbb0e6b..8b1a1a9 100644
--- a/bison/bison.nm
+++ b/bison/bison.nm
@@ -4,7 +4,7 @@
###############################################################################
name = bison
-version = 2.7
+version = 2.7.1
release = 1
groups = Development/Tools
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2013-05-30 9:29 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=20130530093007.599FE200BE@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