From: ludo@gnu.org (Ludovic Courtès)
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 27157@debbugs.gnu.org
Subject: bug#27157: [PATCH] Re: bug#27157: Building Guile 2.2 "times out"
Date: Sun, 04 Jun 2017 15:26:26 +0200 [thread overview]
Message-ID: <8760gbj33x.fsf@gnu.org> (raw)
In-Reply-To: <87d1akpt29.fsf@gmail.com> (Maxim Cournoyer's message of "Sat, 03 Jun 2017 16:09:18 -0700")
Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
>
> [...]
>
>>>> At any rate, it would be good to remove ‘max-silent-time’ from all the
>>>> ‘%default-options’ variables, for consistency.
>>>>
>>>> Ludo’.
>>>
>>> I agree! In my view, interactive user commands should expect the users
>>> to take action themselves (e.g.; user notice no output for 3 hours; hits
>>> C-c. Or, user notice no output for 3 hours, check the process in top,
>>> sees it's still doing something, decides to leave it running a couple
>>> more hours).
>>
>> Yes. Would you like to prepare a patch to remove ‘max-silent-time’ from
>> all the ‘%default-options’?
>
> I gave this a quick try, but got confused upon encountering the
> guix-offload script; it has a max-silent-time option, but doesn't build
> anything, it simply copies stuff IIUC.
>
> Should we remove it there as well?
No: ‘guix offload’ gets max-silent-time systematically from its
command-line arguments (it is invoked by guix-daemon). So this one can
remain as-is.
Ludo’.
next prev parent reply other threads:[~2017-06-04 13:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 4:11 bug#27157: Building Guile 2.2 "times out" Maxim Cournoyer
2017-05-31 11:44 ` Ricardo Wurmus
2017-05-31 21:01 ` Ludovic Courtès
2017-06-01 16:06 ` Maxim Cournoyer
2017-06-01 21:37 ` Ludovic Courtès
2017-06-03 20:38 ` bug#27157: [PATCH] " Maxim Cournoyer
2017-06-03 21:37 ` Ludovic Courtès
2017-06-03 23:09 ` Maxim Cournoyer
2017-06-04 13:26 ` Ludovic Courtès [this message]
2017-08-31 13:19 ` Maxim Cournoyer
2017-09-01 9:10 ` Ludovic Courtès
2017-06-03 0:57 ` Mark H Weaver
2017-06-03 7:48 ` Ricardo Wurmus
2017-06-07 23:17 ` Mark H Weaver
2017-06-07 23:35 ` Maxim Cournoyer
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=8760gbj33x.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=27157@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.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.