From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 55d9b88b0ce51e95ddb83c01877b25d1a91f1f97
Date: Sat, 02 Mar 2013 17:12:38 +0100 [thread overview]
Message-ID: <20130302161239.6D51920114@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1712 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 55d9b88b0ce51e95ddb83c01877b25d1a91f1f97 (commit)
via 9eee25f28cdf5538f47f5d123e54ec5b76586bba (commit)
from be1c6800e8546d20fbbbd959895dcb8b4970550a (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 55d9b88b0ce51e95ddb83c01877b25d1a91f1f97
Merge: be1c680 9eee25f
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Sat Mar 2 17:12:33 2013 +0100
Merge remote-tracking branch 'stevee/file-update'
commit 9eee25f28cdf5538f47f5d123e54ec5b76586bba
Author: Stefan Schantl <stefan.schantl(a)ipfire.org>
Date: Sat Mar 2 17:08:33 2013 +0100
file: Update to 5.12.
This is a Minor release to the latest stable version.
Fixes #10279.
-----------------------------------------------------------------------
Summary of changes:
file/file.nm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/file/file.nm b/file/file.nm
index a0bd7ef..c9f1f67 100644
--- a/file/file.nm
+++ b/file/file.nm
@@ -4,7 +4,7 @@
###############################################################################
name = file
-version = 5.11
+version = 5.12
release = 1
groups = System/Tools
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2013-03-02 16: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=20130302161239.6D51920114@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