From: "Clément Lassieur" <clement@lassieur.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 33519@debbugs.gnu.org
Subject: [bug#33519] [PATCH 0/4] Reporting grafts in the user interface
Date: Fri, 30 Nov 2018 12:56:14 +0100 [thread overview]
Message-ID: <87d0qmhj8h.fsf@lassieur.org> (raw)
In-Reply-To: <87ftvn3py6.fsf@elephly.net>
Ricardo Wurmus <rekado@elephly.net> writes:
> Clément Lassieur <clement@lassieur.org> writes:
>
>> Ludovic Courtès <ludo@gnu.org> writes:
>>
>>> Hello Guix!
>>>
>>> These patches add UI hints so that grafting derivations can be
>>> distinguished from more expensive derivations, as suggested by
>>> Ricardo a while back.
>>
>> [...]
>>
>>> Overall this makes operations more transparent. Advanced users
>>> will know what this means, and hopefully others will notice that
>>> grafting is a relatively fast operation and discover that it has to
>>> do with security updates.
>>>
>>> Thoughts?
>>
>> This is awesome!
>
> I agree! This looks great.
>
>> And I imagine it will allow to distinguish packages
>> and tests in Cuirass :-)
>
> How would that work?
As a way to link Cuirass packages to tools like hpcguix-web. It's not a
priority though.
next prev parent reply other threads:[~2018-11-30 11:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 21:43 [bug#33519] [PATCH 0/4] Reporting grafts in the user interface Ludovic Courtès
2018-11-26 21:47 ` [bug#33519] [PATCH 1/4] derivations: Add properties Ludovic Courtès
2018-11-26 21:47 ` [bug#33519] [PATCH 2/4] grafts: Record metadata as derivation properties Ludovic Courtès
2018-11-26 21:47 ` [bug#33519] [PATCH 3/4] status: Report grafting derivations specially Ludovic Courtès
2018-11-26 21:47 ` [bug#33519] [PATCH 4/4] ui: 'show-what-to-build' reports grafts separately Ludovic Courtès
2018-11-27 7:50 ` [bug#33519] [PATCH 0/4] Reporting grafts in the user interface Clément Lassieur
2018-11-27 8:05 ` Ricardo Wurmus
2018-11-28 9:41 ` Ludovic Courtès
2018-11-30 11:56 ` Clément Lassieur [this message]
2018-11-27 8:27 ` 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=87d0qmhj8h.fsf@lassieur.org \
--to=clement@lassieur.org \
--cc=33519@debbugs.gnu.org \
--cc=rekado@elephly.net \
/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.