unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Leo Famulari <leo@famulari.name>
To: swedebugia <swedebugia@riseup.net>
Cc: Mark H Weaver <mhw@netris.org>, Guix-Help <help-guix@gnu.org>
Subject: Re: Ever-growing store with --gc-keep-outputs?
Date: Tue, 13 Nov 2018 15:31:56 -0500	[thread overview]
Message-ID: <20181113203156.GB11922@jasmine.lan> (raw)
In-Reply-To: <a6b4f528-3799-35ad-8b10-93c6d33ff5cb@riseup.net>

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

On Fri, Nov 09, 2018 at 05:47:47PM +0100, swedebugia wrote:
> Thanks for the heads up! I totally agree. Guix is way too silent to my
> taste, comparing with e.g. pacman and git.

Now we are ready to discuss the color of the bike shed ... ;)

But I think the best way is to make the software "just work", so that it
can be silent and not make the user wish for more verbose comments. This
is definitely possible — a lot of software is like this. It's so
reliable that we forget there are computer programs running there.

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

  reply	other threads:[~2018-11-13 20:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-11 19:11 Ever-growing store with --gc-keep-outputs? Pierre Neidhardt
2018-09-12 10:55 ` Pierre Neidhardt
2018-09-13  9:09 ` Ludovic Courtès
2018-09-13  9:32   ` Pierre Neidhardt
2018-09-14  9:51     ` Ludovic Courtès
2018-09-14 10:57       ` Pierre Neidhardt
2018-09-14 17:46         ` Mark H Weaver
2018-09-14 18:02           ` Pierre Neidhardt
2018-09-14 21:34             ` Mark H Weaver
2018-09-14 22:10               ` Pierre Neidhardt
2018-11-09  6:53           ` swedebugia
2018-11-09  7:13             ` Mark H Weaver
2018-11-09 10:58               ` Pierre Neidhardt
2018-11-09 16:47                 ` swedebugia
2018-11-13 20:31                   ` Leo Famulari [this message]
2018-11-13 21:14                     ` swedebugia

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=20181113203156.GB11922@jasmine.lan \
    --to=leo@famulari.name \
    --cc=help-guix@gnu.org \
    --cc=mhw@netris.org \
    --cc=swedebugia@riseup.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.
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).