From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 3cf9dba6b4d36d320a8994820569f200c03f1d36
Date: Tue, 05 Nov 2024 16:49:41 +0000 [thread overview]
Message-ID: <4XjZ7T11SPz2xYv@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1741 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 3cf9dba6b4d36d320a8994820569f200c03f1d36 (commit)
from 6ccbd48aa9b999880c5944e9c1eb2bb1dca81b13 (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 3cf9dba6b4d36d320a8994820569f200c03f1d36
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Tue Nov 5 17:48:17 2024 +0100
network-functions: fix add newline in $wireless_status
with the other syntax perl suggest this change.
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/cfgroot/network-functions.pl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/cfgroot/network-functions.pl b/config/cfgroot/network-functions.pl
index 37eaf69cc..37a436253 100644
--- a/config/cfgroot/network-functions.pl
+++ b/config/cfgroot/network-functions.pl
@@ -438,7 +438,7 @@ sub _get_wireless_status($) {
my $intf = shift;
if (!$wireless_status{$intf}) {
- $wireless_status{$intf} = join(/\n/, &General::system_output("iw", "dev", "$intf", "link"));
+ $wireless_status{$intf} = join("\n", &General::system_output("iw", "dev", "$intf", "link"));
}
return $wireless_status{$intf};
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2024-11-05 16:49 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=4XjZ7T11SPz2xYv@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