From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 7074aa599517227298413f9eb6b3ae0767d2217e
Date: Mon, 21 Mar 2016 12:26:11 +0000 [thread overview]
Message-ID: <20160321122611.803FB1081BA6@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1782 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 7074aa599517227298413f9eb6b3ae0767d2217e (commit)
from cadcad57788eaa48548e23b96925ef295226652d (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 7074aa599517227298413f9eb6b3ae0767d2217e
Author: Alexander Marx <alexander.marx(a)ipfire.org>
Date: Mon Mar 21 12:35:26 2016 +0100
acpid: Update to Version 2.0.27
Signed-off-by: Alexander Marx <alexander.marx(a)ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
acpid/acpid.nm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/acpid/acpid.nm b/acpid/acpid.nm
index 0973b03..f13dfe4 100644
--- a/acpid/acpid.nm
+++ b/acpid/acpid.nm
@@ -4,7 +4,7 @@
###############################################################################
name = acpid
-version = 2.0.16
+version = 2.0.27
release = 1
# ACPI is only available on x86 architectures.
@@ -19,7 +19,7 @@ description
acpid is a daemon that dispatches ACPI events to user-space programs.
end
-source_dl = http://tedfelix.com/linux/
+source_dl = https://sourceforge.net/projects/acpid2/files/
sources = %{thisapp}.tar.xz
build
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2016-03-21 12:26 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=20160321122611.803FB1081BA6@git01.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