From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 02a43f996a257b62d81d344f4fb3f07bd61bd854
Date: Mon, 04 Feb 2013 00:01:37 +0100 [thread overview]
Message-ID: <20130203230141.5C08B200B5@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1593 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 02a43f996a257b62d81d344f4fb3f07bd61bd854 (commit)
from 6ef17b234987286eec1f077f8fecf78a5a926a19 (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 02a43f996a257b62d81d344f4fb3f07bd61bd854
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Sun Feb 3 22:41:47 2013 +0000
lm-sensors: Add development package.
This package comes with development headers, so
we need to package into their own package.
-----------------------------------------------------------------------
Summary of changes:
lm-sensors/lm-sensors.nm | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
Difference in files:
diff --git a/lm-sensors/lm-sensors.nm b/lm-sensors/lm-sensors.nm
index 2cee295..8ab6c38 100644
--- a/lm-sensors/lm-sensors.nm
+++ b/lm-sensors/lm-sensors.nm
@@ -5,7 +5,7 @@
name = lm-sensors
version = 3.3.3
-release = 1
+release = 2
thisapp = lm_sensors-%{version}
groups = Applications/Statistics
@@ -57,6 +57,10 @@ packages
end
end
+ package %{name}-devel
+ template DEVEL
+ end
+
package %{name}-debuginfo
template DEBUGINFO
end
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2013-02-03 23:01 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=20130203230141.5C08B200B5@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