From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. d5d3748b0269ffa8162f99dac1ae53d72be62bda
Date: Wed, 30 Mar 2022 15:53:23 +0000 [thread overview]
Message-ID: <4KT9vS08L3z2xjF@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1636 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, master has been updated
via d5d3748b0269ffa8162f99dac1ae53d72be62bda (commit)
from 21de246ef71f1858205157cdc7ffb380d98e35b4 (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 d5d3748b0269ffa8162f99dac1ae53d72be62bda
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Wed Mar 30 15:50:55 2022 +0000
backup: Move empty check to the correct place
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/backup/backup.pl | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Difference in files:
diff --git a/config/backup/backup.pl b/config/backup/backup.pl
index 2e9c0c573..8ea399bb9 100644
--- a/config/backup/backup.pl
+++ b/config/backup/backup.pl
@@ -37,11 +37,11 @@ list_addons() {
process_includes() {
local include
for include in $@; do
- # Skip any empty line (which will include /)
- [ -n "${include}" ] || continue
-
local file
while read -r file; do
+ # Skip any empty line (which will include /)
+ [ -n "${file}" ] || continue
+
for file in /${file}; do
if [ -e "${file}" ]; then
echo "${file}"
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2022-03-30 15:53 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=4KT9vS08L3z2xjF@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