From: "Ludovic Courtès" <ludo@gnu.org>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 42481@debbugs.gnu.org
Subject: [bug#42481] [PATCH 0/2] Printing a more concise build plan
Date: Mon, 03 Aug 2020 17:49:25 +0200 [thread overview]
Message-ID: <877dufspa2.fsf@gnu.org> (raw)
In-Reply-To: <87wo2jlf9x.fsf@gnu.org> (Mathieu Othacehe's message of "Fri, 31 Jul 2020 20:18:18 +0200")
Hi!
Mathieu Othacehe <othacehe@gnu.org> skribis:
> Most of the times, I'm reading the build plan only for one purpose, stop
> the command if I'm going to build (too many) things.
>
> Trying to think more like a newcomer (recent DistroTube video helps in that
> matter), I feel like information such as grafts and profile hooks are
> way too low level.
Yeah, that’s also my feeling.
Marius Bakke <marius@gnu.org> skribis:
> I think it looks great. It's good that 'guix build' retains the
> previous verbosity, and that 'guix upgrade' et.al still prints the
> profile derivation, but omits the uninteresting stuff. LGTM!
Alright, pushed as 898e6d0a07e4260600d0876d8d1f551ac8b647f9, thanks!
Ludo’.
next prev parent reply other threads:[~2020-08-03 15:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 21:40 [bug#42481] [PATCH 0/2] Printing a more concise build plan Ludovic Courtès
2020-07-22 21:46 ` [bug#42481] [PATCH 1/2] ui: Add #:verbosity to 'show-what-to-build' Ludovic Courtès
2020-07-22 21:46 ` [bug#42481] [PATCH 2/2] scripts: Pass #:verbosity to 'build-notifier' Ludovic Courtès
2020-07-31 16:34 ` [bug#42481] [PATCH 0/2] Printing a more concise build plan Ludovic Courtès
2020-07-31 18:18 ` Mathieu Othacehe
2020-08-03 15:49 ` Ludovic Courtès [this message]
2020-07-31 19:03 ` Marius Bakke
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=877dufspa2.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=42481@debbugs.gnu.org \
--cc=othacehe@gnu.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.
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).