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. 82e65a3a5461514436808f38896146650fd21cf7
Date: Sat, 11 Feb 2023 16:36:38 +0000	[thread overview]
Message-ID: <4PDbpZ5Y1pz2xmQ@people01.haj.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2019 bytes --]

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  82e65a3a5461514436808f38896146650fd21cf7 (commit)
       via  8284f978db00f1764cde8058b4005f81cadbe286 (commit)
       via  c8bcc3364f4087e35749eb587552a83d0da9e70a (commit)
      from  fa94326f5d826c8d8cb92ca75f61e3588acd632f (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 82e65a3a5461514436808f38896146650fd21cf7
Merge: fa94326f5 8284f978d
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Sat Feb 11 16:36:13 2023 +0000

    Merge branch 'master' into next

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

Summary of changes:
 lfs/linux | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

Difference in files:
diff --git a/lfs/linux b/lfs/linux
index 1153794f6..6c1b762a7 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -24,7 +24,7 @@
 
 include Config
 
-VER         = 6.1.10
+VER         = 6.1.11
 ARM_PATCHES = 6.1.y-ipfire0
 
 THISAPP    = linux-$(VER)
@@ -74,7 +74,7 @@ objects = \
 
 $(DL_FILE)					= $(URL_IPFIRE)/$(DL_FILE)
 
-$(DL_FILE)_BLAKE2 = 926c499eb3260e4358b8112785e7be74062aca54b4d5c21d2729efc81329ae168c461d32f54061d8db05a12cac45b63ca97b74084a8af8138f547c3a2fc2d947
+$(DL_FILE)_BLAKE2 = 2a1dc1acd63308d72a927f39bc5a9be0bc220673655422c90113300598e754d16021cec85751044114d161a82e476473896bd778180d889d54917ce19d176b4c
 arm-multi-patches-$(ARM_PATCHES).patch.xz_BLAKE2 = 3ef9a778c5c41ee8bf2942a48f63b21228a632a2910d2123f01155bbf571592898cffffa61c387a5a6c817b62e458947b4c406c6591b23b5401faa47b020337f
 
 install : $(TARGET)


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

                 reply	other threads:[~2023-02-11 16:36 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=4PDbpZ5Y1pz2xmQ@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