From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 66ac8193fece9902f85504a7dba994aa2642ac60
Date: Tue, 04 Dec 2012 23:57:44 +0100 [thread overview]
Message-ID: <20121204225746.2C5F620210@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1660 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 66ac8193fece9902f85504a7dba994aa2642ac60 (commit)
via 3ffb916517ad42d51fe8e7647cea2ca6e20e4689 (commit)
from 67ae211c33e8734f14e0fc5a2074fcf1ff232618 (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 66ac8193fece9902f85504a7dba994aa2642ac60
Merge: 67ae211 3ffb916
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Tue Dec 4 23:57:18 2012 +0100
Merge remote-tracking branch 'stevee/pcre'
commit 3ffb916517ad42d51fe8e7647cea2ca6e20e4689
Author: Stefan Schantl <stefan.schantl(a)ipfire.org>
Date: Tue Dec 4 19:58:22 2012 +0100
pcre: Update to 8.32.
Fixes #10261.
-----------------------------------------------------------------------
Summary of changes:
pcre/pcre.nm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/pcre/pcre.nm b/pcre/pcre.nm
index 065754b..8e1797b 100644
--- a/pcre/pcre.nm
+++ b/pcre/pcre.nm
@@ -4,8 +4,8 @@
###############################################################################
name = pcre
-version = 8.31
-release = 2
+version = 8.32
+release = 1
compat_version = 8.21
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2012-12-04 22:57 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=20121204225746.2C5F620210@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