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, next, updated. f9efedaae8288c9b66368d81df47cc70286bf80f
Date: Fri, 20 Nov 2026 12:56:17 +0000 (UTC)	[thread overview]
Message-ID: <4jWFhK3PNYz2xVM@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  f9efedaae8288c9b66368d81df47cc70286bf80f (commit)
       via  14700fccf800f0f300236cfebb8d2c2f23e91028 (commit)
       via  13c682f328b7beaa7dc2931ef2cecb2f2d077b8c (commit)
       via  ca76d30408a9841bc2dc703b539ac43e42e4117c (commit)
       via  1aaae7af631fd6c46713c3804c1928131d5356ea (commit)
       via  2324c4306b402399efb8a0a92c17e7eab5dc372b (commit)
      from  c5619995cb5b1dd6173e97e3e898dd927901e5ae (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 f9efedaae8288c9b66368d81df47cc70286bf80f
Merge: c5619995c 14700fccf
Author: Michael Tremer <michael.tremer@ipfire.org>
Date:   Fri Nov 20 12:56:10 2026 +0000

    Merge branch 'master' into next

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

Summary of changes:

Difference in files:


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


                 reply	other threads:[~2026-11-20 12:56 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=4jWFhK3PNYz2xVM@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