all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 29406@debbugs.gnu.org
Subject: [bug#29406] [PATCH core-updates]: Add selected upstream fixes for glibc 2.26.
Date: Tue, 28 Nov 2017 13:26:44 -0500	[thread overview]
Message-ID: <20171128182644.GG14200@jasmine.lan> (raw)
In-Reply-To: <878teqzhpa.fsf@fastmail.com>

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

On Tue, Nov 28, 2017 at 01:54:57PM +0100, Marius Bakke wrote:
> Gah.  I used "xz --threads=0" initially and didn't expect it to change
> the outcome.

Since threads=0 means "compress with as many CPU cores as are
available", I'd guess the output of this depends on the number of
threads used.

from man(1):
"Setting threads to a special value 0 makes xz use as many threads as
there are CPU cores on the system."

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

  parent reply	other threads:[~2017-11-28 18:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-22 21:28 [bug#29406] [PATCH core-updates]: Add selected upstream fixes for glibc 2.26 Marius Bakke
2017-11-23 14:57 ` Leo Famulari
2017-11-24  1:12   ` Marius Bakke
2017-11-24  3:08     ` Marius Bakke
2017-11-27 21:30   ` Leo Famulari
2017-11-28  1:42     ` Marius Bakke
2017-11-28 10:45       ` Ludovic Courtès
2017-11-28 12:54         ` Marius Bakke
2017-11-28 16:03           ` bug#29406: " Ludovic Courtès
2017-11-28 17:16             ` [bug#29406] " Marius Bakke
2017-11-28 21:02               ` Ludovic Courtès
2017-11-28 21:42                 ` Leo Famulari
2017-11-29 16:40                   ` Ludovic Courtès
2017-11-28 18:26           ` Leo Famulari [this message]
2017-11-23 15:42 ` Ludovic Courtès

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=20171128182644.GG14200@jasmine.lan \
    --to=leo@famulari.name \
    --cc=29406@debbugs.gnu.org \
    --cc=mbakke@fastmail.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.