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: 60564@debbugs.gnu.org
Subject: [bug#60564] [PATCH] scripts: refresh: Add -T option.
Date: Wed, 11 Jan 2023 14:43:59 -0500	[thread overview]
Message-ID: <87wn5shn5s.fsf@gmail.com> (raw)
In-Reply-To: <20230105011032.18623-1-jgart@dismail.de> (jgart@dismail.de's message of "Wed, 4 Jan 2023 19:10:32 -0600")

Hi,

jgart <jgart@dismail.de> writes:

> * doc/guix.texi (Invoking guix refresh): Document the -T option.
> * guix/scripts/refresh.scm (%options): Add the -T flag.
> ---
>  doc/guix.texi            | 1 +
>  guix/scripts/refresh.scm | 4 ++--
>  2 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/doc/guix.texi b/doc/guix.texi
> index 96b4675a01..e3ecf1f148 100644
> --- a/doc/guix.texi
> +++ b/doc/guix.texi
> @@ -14197,6 +14197,7 @@ for compatibility with an upgraded @code{flex} package.
>  @table @code
>  
>  @item --list-transitive
> +@item --T

The above should be -T, right?

I wonder if this option is common enough to need a dedicated short
switch?  I use it sparingly myself; typically I use '-l' to know which
packages I'd impact.

The rest looks OK.

-- 
Thanks,
Maxim




  parent reply	other threads:[~2023-01-11 19:45 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 ` Maxim Cournoyer [this message]
2023-03-03  8:56   ` [bug#60564] [PATCH] scripts: refresh: Add -T option 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
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=87wn5shn5s.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=60564@debbugs.gnu.org \
    --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).