From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 6b184642d25460d406c9d706fa985a25ca354639
Date: Sun, 30 Jan 2022 08:51:29 +0000 [thread overview]
Message-ID: <4JmlKt1cHdz2xmn@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1503 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 6b184642d25460d406c9d706fa985a25ca354639 (commit)
from 2ebbe5e105fdcf1c0367060deda5c190b432b96b (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 6b184642d25460d406c9d706fa985a25ca354639
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun Jan 30 08:50:22 2022 +0000
leds: fix R4S sys led name at shutdown
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
src/initscripts/system/leds | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/src/initscripts/system/leds b/src/initscripts/system/leds
index 3a0d3f20d..d68426acf 100644
--- a/src/initscripts/system/leds
+++ b/src/initscripts/system/leds
@@ -173,7 +173,7 @@ case "${1}" in
# Nanopi R4S stop
disable_led_trigger nanopi-r4s:green:sys
- enable_led nanopi-r4s:red:sys
+ enable_led nanopi-r4s:green:sys
disable_led_trigger nanopi-r4s:green:wan
disable_led_trigger nanopi-r4s:green:lan
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2022-01-30 8:51 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=4JmlKt1cHdz2xmn@people01.haj.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