diff mbox series

[bug#68738,5/7] gnu: linux-libre 5.10: Update to 5.10.209.

Message ID 20240126151222.11209-5-w@wmeyer.eu
State New
Headers show
Series linux-libre kernel updates (2024-01-25) | expand

Commit Message

Wilko Meyer Jan. 26, 2024, 3:12 p.m. UTC 
* gnu/packages/linux.scm (linux-libre-5.10-version): Update to 5.10.209.
(linux-libre-5.10-pristine-source): Update hashes.
---
 gnu/packages/linux.scm | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

Comments

Clément Lassieur Jan. 26, 2024, 10:21 p.m. UTC | #1 
Just a small tip:

The point of sending an email to xxxxx-done@debbugs.gnu.org is that you
actually send an email explaining why it's closed.

If you don't want to send an email to human people, you can just mail
control@debbugs.gnu.org, with no subject, and with content: "close
xxxxx".  (It won't get into people's inbox.)

Explanations here: https://debbugs.gnu.org/server-control.html.

Of course it's better to explain why a bug report is closed.

Cheers,
Clément
Wilko Meyer Jan. 27, 2024, 11:24 p.m. UTC | #2 
Hi Clément,

Clément Lassieur <clement@lassieur.org> writes:

> If you don't want to send an email to human people, you can just mail
> control@debbugs.gnu.org, with no subject, and with content: "close
> xxxxx".  (It won't get into people's inbox.)
>
> Explanations here: https://debbugs.gnu.org/server-control.html.

Thanks for the tip & for taking the time to explain this to me! This
would've been the better option (accidentally send a patch-series to
guix-patches@debbugs.gnu.org instead of to the specific issue created by
the cover letter, so I had to clean up wrongfully created issues) in
this case and would've caused less clutter. I'll take some time to read
up on the debbugs documentation as I'm not too familiar with it as a
tool yet!
Clément Lassieur Jan. 28, 2024, 12:36 a.m. UTC | #3 
Well don't worry this happened to all of us ;)

Welcome

On Sat, Jan 27, 2024, at 11:24 PM, Wilko Meyer wrote:
> 
> Hi Clément,
> 
> Clément Lassieur <clement@lassieur.org> writes:
> 
> > If you don't want to send an email to human people, you can just mail
> > control@debbugs.gnu.org, with no subject, and with content: "close
> > xxxxx".  (It won't get into people's inbox.)
> >
> > Explanations here: https://debbugs.gnu.org/server-control.html.
> 
> Thanks for the tip & for taking the time to explain this to me! This
> would've been the better option (accidentally send a patch-series to
> guix-patches@debbugs.gnu.org instead of to the specific issue created by
> the cover letter, so I had to clean up wrongfully created issues) in
> this case and would've caused less clutter. I'll take some time to read
> up on the debbugs documentation as I'm not too familiar with it as a
> tool yet!
> 
> -- 
> Kind regards,
> 
> Wilko Meyer
> w@wmeyer.eu
>
diff mbox series

Patch

diff --git a/gnu/packages/linux.scm b/gnu/packages/linux.scm
index b4e3cf0c70..0a563c013c 100644
--- a/gnu/packages/linux.scm
+++ b/gnu/packages/linux.scm
@@ -561,7 +561,7 @@  (define-public linux-libre-5.15-pristine-source
                             (%upstream-linux-source version hash)
                             deblob-scripts-5.15)))
 
-(define-public linux-libre-5.10-version "5.10.208")
+(define-public linux-libre-5.10-version "5.10.209")
 (define-public linux-libre-5.10-gnu-revision "gnu1")
 (define deblob-scripts-5.10
   (linux-libre-deblob-scripts
@@ -571,7 +571,7 @@  (define deblob-scripts-5.10
    (base32 "0zmmqj5gyiy2q81f199c29b14isfiqbvl87y72k14yy0q5398276")))
 (define-public linux-libre-5.10-pristine-source
   (let ((version linux-libre-5.10-version)
-        (hash (base32 "0vpvy47cmcinhs76cjl2n81zrlhbqgpi4v29izn2hzsl15x189ch")))
+        (hash (base32 "1mc8rssk5aypgb58jz6i2bbflfr6qh1kgqpam0k8fqvwcjnjzqj4")))
    (make-linux-libre-source version
                             (%upstream-linux-source version hash)
                             deblob-scripts-5.10)))