unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: jgart <jgart@dismail.de>, 63036@debbugs.gnu.org
Subject: bug#63036: -v or --verbose CLI argument input is undocumented in the CLI
Date: Tue, 25 Apr 2023 14:36:24 +0200	[thread overview]
Message-ID: <86cz3sb0l3.fsf@gmail.com> (raw)
In-Reply-To: <00781330fbd65f97724d7c93d9b87f09@dismail.de>

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

Hi,

On Sun, 23 Apr 2023 at 15:27, "jgart" via Bug reports for GNU Guix <bug-guix@gnu.org> wrote:

> Hmmm, what is the type and/or range of inputs that are valid for
> LEVEL?

What about this patch?


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: p.patch --]
[-- Type: text/x-diff, Size: 796 bytes --]

diff --git a/guix/scripts/build.scm b/guix/scripts/build.scm
index 72a24f91ac..35cb888c3b 100644
--- a/guix/scripts/build.scm
+++ b/guix/scripts/build.scm
@@ -452,8 +452,10 @@ (define (show-help)
   -r, --root=FILE        make FILE a symlink to the result, and register it
                          as a garbage collector root"))
   (display (G_ "
-  -v, --verbosity=LEVEL  use the given verbosity LEVEL"))
-  (display (G_ "
+  -v, --verbosity=LEVEL  use the given verbosity LEVEL, range 0-3
+                         0 = no output, 1 = quiet, 2 = 1 + download URLs,
+                         3 = all on standard error"))
+    (display (G_ "
   -q, --quiet            do not show the build log"))
   (display (G_ "
       --log-file         return the log file names for the given derivations"))

[-- Attachment #3: Type: text/plain, Size: 16 bytes --]



Cheers,
simon

      reply	other threads:[~2023-04-27 13:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-23 15:27 bug#63036: -v or --verbose CLI argument input is undocumented in the CLI jgart via Bug reports for GNU Guix
2023-04-25 12:36 ` Simon Tournier [this message]

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=86cz3sb0l3.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=63036@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).