public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core195, created. 27ec6f7860da27d046ddeb33809eba897b0766e7
Date: Sun, 15 Jun 2025 12:00:03 +0000 (UTC)	[thread overview]
Message-ID: <4bKsBq2PPTz2xc5@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, core195 has been created
        at  27ec6f7860da27d046ddeb33809eba897b0766e7 (commit)

- Log -----------------------------------------------------------------
commit 27ec6f7860da27d046ddeb33809eba897b0766e7
Author: Michael Tremer <michael.tremer@ipfire.org>
Date:   Sun Jun 1 17:00:51 2025 +0200

    wireguard: Don't try to delete any interfaces that don't exist
    
    When the WireGuard interfaces are being destroyed, we are using some
    globbing to identify the right interfaces. If there are no interfaces
    the globbing string does not match anything and is returned itself. To
    avoid an error when trying to delete an interface that never existed, we
    configure the shell to never expand empty globbings.
    
    Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>

commit 9ef726eeb272104656baf3c38eca75c4dc5bea10
Author: Michael Tremer <michael.tremer@ipfire.org>
Date:   Sun Jun 1 15:19:13 2025 +0200

    wireguard-functions.pl: Fix ListenPort
    
    The option was incorrectly named "Port" before.
    
    Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>

-----------------------------------------------------------------------


hooks/post-receive
--
IPFire 2.x development tree


             reply	other threads:[~2025-06-15 12:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-15 12:00 Michael Tremer [this message]
2025-06-16 10:00 Michael Tremer

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=4bKsBq2PPTz2xc5@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