From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree tag, v2.29-core200, created. 6b37324b0a6e2f99a44fdf71238632ebb0d32a82
Date: Tue, 21 Apr 2026 09:18:15 +0000 (UTC) [thread overview]
Message-ID: <4g0Gx34W9Jz2xTH@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 tag, v2.29-core200 has been created
at 6b37324b0a6e2f99a44fdf71238632ebb0d32a82 (commit)
- Log -----------------------------------------------------------------
commit 6b37324b0a6e2f99a44fdf71238632ebb0d32a82
Author: Adolf Belka <adolf.belka@ipfire.org>
Date: Mon Feb 23 20:45:14 2026 +0100
dehydrated: Fix for bug13945 - not renewing certificates within period of 32 days before expiring
- Application of two commits that will end up as part of 0.7.3 eventually.
Fixes: bug13945
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
-----------------------------------------------------------------------
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2026-04-21 9:18 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=4g0Gx34W9Jz2xTH@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