public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: mark@klomp.org,  binutils@sourceware.org,  gdb-patches@sourceware.org
Subject: Re: [PATCH] src-release.sh: Use -T0 for xz compression
Date: Fri, 31 May 2024 13:54:40 +0100	[thread overview]
Message-ID: <87y17qcfan.fsf@gentoo.org> (raw)
In-Reply-To: <86wmnapl5o.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 31 May 2024 09:09:39 +0300")

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

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Sam James <sam@gentoo.org>
>> Cc: binutils@sourceware.org,  gdb-patches@sourceware.org
>> Date: Thu, 30 May 2024 22:56:50 +0100
>> 
>> > On my machine (using 4 cores) this reduces the time to create
>> > binutils-2.42.50.tar.xz from 1 minute 40 seconds to 56 seconds.
>> >
>> > xz has supported -T0 since version 5.2.0 (released 2014-12-21).
>> 
>> LGTM and it's the default from >=5.6.0 anyway.
>
> The same 5.6.0 which introduced the backdoor?  How are its defaults
> relevant, when no one in their right mind will ever use those
> versions??

xz continues as a project after this incident and fixed releases were
issued 2 days ago. I'm not sure what your point is here.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]

  reply	other threads:[~2024-05-31 12:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-30 21:43 Mark Wielaard
2024-05-30 21:56 ` Sam James
2024-05-30 21:59   ` Sam James
2024-05-31  6:09   ` Eli Zaretskii
2024-05-31 12:54     ` Sam James [this message]
2024-06-03  9:36   ` Mark Wielaard

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=87y17qcfan.fsf@gentoo.org \
    --to=sam@gentoo.org \
    --cc=binutils@sourceware.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=mark@klomp.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).