From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 37b16f78dd119b61f30191c65d6a8dcc36c2bb80
Date: Mon, 2 Jun 2025 16:01:43 +0000 (UTC) [thread overview]
Message-ID: <4b9z9g60Ncz2xhb@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 37b16f78dd119b61f30191c65d6a8dcc36c2bb80 (commit)
via 8a31117c0cc6c07aaadfe63f99cfda4c7a6b6ec3 (commit)
from e38cf1e2cd33d19f34f0856a87e09014a7cd4f45 (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 37b16f78dd119b61f30191c65d6a8dcc36c2bb80
Merge: e38cf1e2cd 8a31117c0c
Author: Michael Tremer <michael.tremer@ipfire.org>
Date: Mon Jun 2 16:01:32 2025 +0000
Merge branch 'master' into next
-----------------------------------------------------------------------
Summary of changes:
Difference in files:
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2025-06-02 16:01 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=4b9z9g60Ncz2xhb@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