From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Current 'next': changes ... check rootfile
Date: Mon, 03 Oct 2022 17:28:56 +0200 [thread overview]
Message-ID: <09de86f6-77e9-b5db-a2ef-6932ef4e05a1@ipfire.org> (raw)
In-Reply-To: <e2cd791a-e300-a865-5221-bba1978d0524@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 453 bytes --]
Ok, forget it - I found it!
On 03.10.2022 15:06, Matthias Fischer wrote:
> Hi,
>
> during the last 'next' builds I'm constantly getting the message that
> somthing has changed:
>
> "Changes in linux-5.15.71-ipfire check rootfile!"
>
> The same goes for the 'nightly builds'.
>
> But what - and where - are these changes!?
>
> I searched. Didn't find the reason. Pulling my hair out... Giving up. ;-)
>
> Anyone has a clue?
>
> Best,
> Matthias
prev parent reply other threads:[~2022-10-03 15:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 13:06 Matthias Fischer
2022-10-03 15:28 ` Matthias Fischer [this message]
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=09de86f6-77e9-b5db-a2ef-6932ef4e05a1@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@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