unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: jgart <jgart@dismail.de>
Cc: Josselin Poiret <dev@jpoiret.xyz>, 60564@debbugs.gnu.org
Subject: [bug#60564] [PATCH] scripts: refresh: Add -T option.
Date: Fri, 03 Mar 2023 22:30:01 -0500	[thread overview]
Message-ID: <875ybh42iu.fsf@gmail.com> (raw)
In-Reply-To: <20230303162135.2864-1-jgart@dismail.de> (jgart@dismail.de's message of "Fri, 3 Mar 2023 17:21:36 +0100")

Hi jgart,

jgart <jgart@dismail.de> writes:

> * doc/guix.texi (Invoking guix refresh): Document the -T option.
> * guix/scripts/refresh.scm (%options): Add the -T flag.
> ---
>
> Hi Josselin and Maxim
>
>> I wonder if this option is common enough to need a dedicated short
>> switch?
>
> I would probably use the option more if it had a short option ;()
>
> I think that it is useful. What would be the negative of adding the short option for it?

Nothing immediately, but we'd have to honor T forever as it'd be part of
the public CLI, loosing that letter for something more useful that may
yet to appear.

Probably an overblown concern, to be honest, eh.

I'll see what Josselin says about it, otherwise I'll push it soon.

-- 
Thanks,
Maxim




  reply	other threads:[~2023-03-04  3:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-05  1:10 [bug#60564] [PATCH] scripts: refresh: Add -T option jgart via Guix-patches via
2023-01-05  1:35 ` [bug#60564] Probably a lost battle Felix Lechner via Guix-patches via
2023-01-11 19:43 ` [bug#60564] [PATCH] scripts: refresh: Add -T option Maxim Cournoyer
2023-03-03  8:56   ` Josselin Poiret via Guix-patches via
2023-03-03 16:43   ` jgart via Guix-patches via
2023-03-03 16:21 ` jgart via Guix-patches via
2023-03-04  3:30   ` Maxim Cournoyer [this message]
2023-03-04 10:51     ` Josselin Poiret via Guix-patches via
2023-03-21 18:56 ` bug#60564: " 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

  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=875ybh42iu.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=60564@debbugs.gnu.org \
    --cc=dev@jpoiret.xyz \
    --cc=jgart@dismail.de \
    /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).