From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, thirteen, updated. b1879b637b00091ff76b32b30032555d4d667e10
Date: Thu, 30 Aug 2012 22:20:32 +0200 [thread overview]
Message-ID: <20120830202032.B857A200A8@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1384 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 2.x development tree".
The branch, thirteen has been updated
via b1879b637b00091ff76b32b30032555d4d667e10 (commit)
from 2b710ab3fa07fa6dbe31cf72c57b21cf30d43418 (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 b1879b637b00091ff76b32b30032555d4d667e10
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Aug 30 22:20:04 2012 +0200
zlib: Provide libz.so.
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/common/zlib | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
Difference in files:
diff --git a/config/rootfiles/common/zlib b/config/rootfiles/common/zlib
index 78620f4..8c46843 100644
--- a/config/rootfiles/common/zlib
+++ b/config/rootfiles/common/zlib
@@ -3,7 +3,7 @@ lib/libz.so.1.2.7
#usr/include/zconf.h
#usr/include/zlib.h
#usr/lib/libz.a
-#usr/lib/libz.so
+usr/lib/libz.so
#usr/lib/pkgconfig
#usr/lib/pkgconfig/zlib.pc
#usr/share/man/man3/zlib.3
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2012-08-30 20:20 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=20120830202032.B857A200A8@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