all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mathieu Lirzin <mthl@openmailbox.org>
To: Eric Bavier <ericbavier@openmailbox.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Plan for 0.9.0
Date: Thu, 15 Oct 2015 14:28:22 +0200	[thread overview]
Message-ID: <874mhsiae1.fsf@openmailbox.org> (raw)
In-Reply-To: <20151014170227.3a293b5a@openmailbox.org> (Eric Bavier's message of "Wed, 14 Oct 2015 17:02:27 -0500")

Eric Bavier <ericbavier@openmailbox.org> writes:

> On Wed, 14 Oct 2015 23:44:39 +0200
> ludo@gnu.org (Ludovic Courtès) wrote:
>
>> Mathieu Lirzin <mthl@openmailbox.org> skribis:
>> 
>> > ludo@gnu.org (Ludovic Courtès) writes:
>> >
>> >> Dunno, I admit I’m not as enthusiastic as the other people here.  :-)
>> >>
>> >> What would ‘guix gc’ (without any option) do?
>> >
>> > Show --help and exit(0)?  ;)
>> 
>> Sure we could do that, but I’m not convinced it’s an improvement.  WDYT?
>
> FWIW, I'm not convinced either.

I think the enthusiasm for changing ‘guix gc’ was induced by somekind of
shared experience of typing it loosely and ending up having to download
a lot of substitutes again.  So maybe we can keep ‘guix gc’ as it is but
make it interactive by listing what is going to be deleted and ask for
confirmation with a [Y/n] prompt.  This solution will also require
somekind of a ‘--force’ option for scripting purposes.

Does it sound better?

--
Mathieu Lirzin

  reply	other threads:[~2015-10-15 12:28 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-12 21:19 Plan for 0.9.0 Ludovic Courtès
2015-10-13 13:15 ` Daniel Pimentel
2015-10-13 14:37   ` Ludovic Courtès
2015-10-13 15:01   ` Alex Vong
2015-10-13 15:27     ` Ricardo Wurmus
2015-10-13 18:26       ` Mathieu Lirzin
2015-10-13 18:30         ` Taylan Ulrich Bayırlı/Kammer
2015-10-14 19:58     ` Ludovic Courtès
2015-10-14 20:06       ` Mathieu Lirzin
2015-10-14 21:44         ` Ludovic Courtès
2015-10-14 22:02           ` Eric Bavier
2015-10-15 12:28             ` Mathieu Lirzin [this message]
2015-10-15 12:33               ` Thompson, David
2015-10-15 12:51                 ` Mathieu Lirzin
2015-10-15 13:10                   ` Thompson, David
2015-10-15 13:15                     ` Daniel Pimentel
2015-10-15 14:11                       ` Christopher Allan Webber
2015-10-15 14:43                         ` Ludovic Courtès
2015-10-15 13:40                     ` Mathieu Lirzin
2015-10-15 15:31                 ` Taylan Ulrich Bayırlı/Kammer
2015-10-15 19:27                   ` Ludovic Courtès
2015-10-16  4:14                 ` Alex Vong
2015-10-16  7:44                   ` Mathieu Lirzin
2015-10-16 11:09                     ` Alex Vong
2015-10-16  8:10                   ` Registering GC roots Ludovic Courtès
2015-10-16 12:56                     ` Alex Vong
2015-10-16 15:41                       ` Ludovic Courtès
2015-10-16 15:55                         ` Alex Vong
2015-10-16 17:21                           ` Andreas Enge
2015-10-16 16:28                         ` Mathieu Lirzin
2015-10-15 14:41               ` Plan for 0.9.0 Ludovic Courtès
2015-10-15 15:07                 ` Mathieu Lirzin
2015-11-02  9:45 ` 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=874mhsiae1.fsf@openmailbox.org \
    --to=mthl@openmailbox.org \
    --cc=ericbavier@openmailbox.org \
    --cc=guix-devel@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 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.