From: Josselin Poiret via Guix-patches via <guix-patches@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>, jgart <jgart@dismail.de>
Cc: 60564@debbugs.gnu.org
Subject: [bug#60564] [PATCH] scripts: refresh: Add -T option.
Date: Sat, 04 Mar 2023 11:51:37 +0100 [thread overview]
Message-ID: <87fsakrdqe.fsf@jpoiret.xyz> (raw)
In-Reply-To: <875ybh42iu.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]
Hi jgart and Maxim,
Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
> 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.
I'm on the fence as well, it doesn't seem like something you would use
very often, compared to eg. `-l` or `-u`, especially if you mention that
you would use the option more often if this was implemented (I'd expect
more of a "I use it all the time but typing it is annoying"). `guix
size` and `guix graph` are the more useful commands imho. What do you
use it for specifically (maybe that would help us understand the
use-case a bit more)?
At the same time, it's probably fine, we don't have many options for
`guix refresh` and it's not like dozens of them will get added overnight
(and they maybe don't deserve a short argument either). I'll leave it
in your hands 🤠.
Best,
--
Josselin Poiret
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]
next prev parent reply other threads:[~2023-03-04 10:52 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
2023-03-04 10:51 ` Josselin Poiret via Guix-patches via [this message]
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=87fsakrdqe.fsf@jpoiret.xyz \
--to=guix-patches@gnu.org \
--cc=60564@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=jgart@dismail.de \
--cc=maxim.cournoyer@gmail.com \
/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).