From: "Peter Müller" <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 678327a8fd166e611b6b7d2d9bc866897b787989
Date: Sun, 03 Apr 2022 16:49:35 +0000 [thread overview]
Message-ID: <4KWfyS2DPHz2y1Q@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1730 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 678327a8fd166e611b6b7d2d9bc866897b787989 (commit)
from c2058ff641deb106fae99ff53ca2c4f36b87f665 (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 678327a8fd166e611b6b7d2d9bc866897b787989
Author: Peter Müller <peter.mueller(a)ipfire.org>
Date: Sun Apr 3 16:49:02 2022 +0000
Config: Fix missing bracket
Reported-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/Config | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/lfs/Config b/lfs/Config
index 6ee44ce35..d4de6550b 100644
--- a/lfs/Config
+++ b/lfs/Config
@@ -347,7 +347,7 @@ endef
define LOAD
@echo -e "$(MESSAGE)Download: $($(notdir $@))"
wget -T 60 -t 1 -nv -U "IPFireSourceGrabber/2.x" $($(notdir $@)) -O $(DIR_TMP)/$(notdir $@)
- [ "$($(notdir $@)_BLAKE2)" = "$(firstword $(shell b2sum $(DIR_TMP)/$(notdir $@))" ] # detect page not found answer
+ [ "$($(notdir $@)_BLAKE2)" = "$(firstword $(shell b2sum $(DIR_TMP)/$(notdir $@)))" ] # detect page not found answer
mv $(DIR_TMP)/$(notdir $@) $(DIR_DL)
endef
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2022-04-03 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=4KWfyS2DPHz2y1Q@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