From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Changes in Intel-Linux-Processor-Microcode-Data-Files-microcode-20220510 check rootfile!
Date: Mon, 30 May 2022 09:32:33 +0100 [thread overview]
Message-ID: <7FFD6C7F-B437-40DF-9BB4-0B84607ADE5B@ipfire.org> (raw)
In-Reply-To: <915A7478-EBB7-42F4-B03B-095C3B15FFF5@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1202 bytes --]
Hello Jon,
Yes, please send a patch with the changes to the list.
-Michael
> On 25 May 2022, at 19:18, Jon Murphy <jcmurphy26(a)gmail.com> wrote:
>
> Peter,
>
> Last night I cloned `ipfire-2.x.git` via this command: git clone git://git.ipfire.org/ipfire-2.x.git
>
> When I ran make build I got this error:
>
> libshout (2.4.3) [ 0 ][ DONE ]
> htop (3.1.2) [ 0 ][ DONE ]
> mpc (0.34) [ DONE ]
> Checking Logfiles for new Files
> Changes in Intel-Linux-Processor-Microcode-Data-Files-microcode-20220510 check rootfile!
> *** Build finished in 1:56:21 [ DONE ]
> jon(a)deb11vm:~/myProject5/ipfire-2.x$
>
> https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=1ad192722a9ecd0b0f0afc008da020b9534e57d6
>
>
> I looked at the log file for the Intel microcode change.
>
> Should I fix? Or do I leave this to you to fix?
>
>
> Jon
>
parent reply other threads:[~2022-05-30 8:32 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <915A7478-EBB7-42F4-B03B-095C3B15FFF5@gmail.com>]
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=7FFD6C7F-B437-40DF-9BB4-0B84607ADE5B@ipfire.org \
--to=michael.tremer@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