From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 71e3937bf12ef727e535267b04ee90ccb7557556
Date: Thu, 30 Jul 2026 15:26:42 +0000 (UTC) [thread overview]
Message-ID: <4h9tN30Nnfz2xpB@people01.haj.ipfire.org> (raw)
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 71e3937bf12ef727e535267b04ee90ccb7557556 (commit)
from 8b32b8e5e46bc0e2e9e26f2581aaa16a3c4b355d (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 71e3937bf12ef727e535267b04ee90ccb7557556
Author: Michael Tremer <michael.tremer@ipfire.org>
Date: Thu Jul 30 15:26:15 2026 +0000
knot-resolver: Compile for a release
This will remove any debugging/assertions from the code.
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/knot-resolver | 1 +
1 file changed, 1 insertion(+)
Difference in files:
diff --git a/lfs/knot-resolver b/lfs/knot-resolver
index daeea4159..3aec36f93 100644
--- a/lfs/knot-resolver
+++ b/lfs/knot-resolver
@@ -71,6 +71,7 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
@$(PREBUILD)
@rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar axf $(DIR_DL)/$(DL_FILE)
cd $(DIR_APP) && meson setup \
+ --buildtype=release \
--prefix=/usr \
-Duser=knot-resolver \
-Dgroup=knot-resolver \
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2026-07-30 15:26 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=4h9tN30Nnfz2xpB@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