From: Leo Prikler <leo.prikler@student.tugraz.at>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: control@debbugs.gnu.org, julien lepiller <roptat@lepiller.eu>,
38649@debbugs.gnu.org
Subject: [bug#38649] [PATCH] Parallelize `guix package`
Date: Tue, 11 May 2021 16:24:56 +0200 [thread overview]
Message-ID: <b8e1e8c817a792318bb6efdc8d6a9abfa4c77f46.camel@student.tugraz.at> (raw)
In-Reply-To: <87lfr9pume.fsf@gnu.org>
close 38649
thanks
Am Mittwoch, den 18.12.2019, 15:37 +0100 schrieb Ludovic Courtès:
> I cannot think of a useful behavior if wait-for-lock were
> implemented.
> Really, as a user, you’d be unable to know what the end result is. I
> don’t see that as very useful. :-)
It took a while, but I feel you've convinced me.
prev parent reply other threads:[~2021-05-11 14:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 14:18 [bug#38649] [PATCH] Parallelize `guix package` Leo Prikler
2019-12-17 14:20 ` Brett Gilio
2019-12-17 14:34 ` Leo Prikler
2019-12-17 14:38 ` Brett Gilio
2019-12-17 14:32 ` Ludovic Courtès
2019-12-17 15:19 ` Leo Prikler
2019-12-17 15:50 ` Julien Lepiller
2019-12-17 16:16 ` Leo Prikler
2019-12-18 14:37 ` Ludovic Courtès
2021-05-11 14:24 ` Leo Prikler [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b8e1e8c817a792318bb6efdc8d6a9abfa4c77f46.camel@student.tugraz.at \
--to=leo.prikler@student.tugraz.at \
--cc=38649@debbugs.gnu.org \
--cc=control@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=roptat@lepiller.eu \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).