From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [IPFire-SCM] [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 38d3bcd5c14b9670163774d02606a4f7045668d6
Date: Fri, 10 Feb 2012 22:24:51 +0100 [thread overview]
Message-ID: <20120210212451.68A38200BF@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1420 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, next has been updated
via 38d3bcd5c14b9670163774d02606a4f7045668d6 (commit)
from 3412d9ef01a9e4f7718f8d05587f1a5748d0632b (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 38d3bcd5c14b9670163774d02606a4f7045668d6
Author: Dirk Wagner <glotzi(a)ipfire.org>
Date: Fri Feb 10 22:23:44 2012 +0100
nut: fixed wrong version in filename
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/packages/nut | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
Difference in files:
diff --git a/config/rootfiles/packages/nut b/config/rootfiles/packages/nut
index 5be3ac6..53935f0 100644
--- a/config/rootfiles/packages/nut
+++ b/config/rootfiles/packages/nut
@@ -69,7 +69,7 @@ usr/lib/libnutscan.so.1.0.0
#usr/lib/libupsclient.la
usr/lib/libupsclient.so
usr/lib/libupsclient.so.1
-usr/lib/libupsclient.so.1.0.0
+usr/lib/libupsclient.so.1.1.0
usr/sbin/upsd
usr/sbin/upsmon
usr/sbin/upssched
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2012-02-10 21:24 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=20120210212451.68A38200BF@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