unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: <ng0@n0.is>
To: Ludovic Court=C3=A8s <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: bug#34020: [PATCH 0/2] Re-purpose '--verbosity' to something useful
Date: Fri, 11 Jan 2019 15:02:52 +0100 (CET)	[thread overview]
Message-ID: <E1ghxOe-0003Mp-EJ@rmmprod05.runbox> (raw)
In-Reply-To: <87fttz8mxu.fsf@gnu.org>

Would you be open for a patch which adds BSD familiar -v behavior?
In other words, multiple v increase the verbosity level, like -vv is more
verbose than -v. I'll have to check the actual changes first, haven't had
access to something which runs plain Guix in a while.

On Fri, 11 Jan 2019 12:15:41 +0100, Ludovic Courtès <ludo@gnu.org> wrote:

> Hi,
> 
> Mike Gerwitz <mtg@gnu.org> skribis:
> 
> > On Wed, Jan 09, 2019 at 14:31:45 +0100, Ludovic Courtès wrote:
> >> These patches re-purposes ‘--verbosity’ so that it better matches
> >> user expectations.  The previous ‘--verbosity’ option, which is
> >> about the daemon’s debugging output, is renamed to ‘--debug’.
> >> In addition, ‘--verbosity’ now has a shorthand ‘-v’.
> >>
> >> Most commands that build stuff support -v/--verbosity so users can
> >> easily override the default verbosity level.
> >>
> >> Thoughts?
> >
> > (Just having looked at the patches, without actually trying it out.)
> >
> > This is much better, thank you!  I was confused by the previous behavior.
> 
> Thanks for your feedback, pushed now!
> 
> I’ve also adjust ‘guix archive’, which I had forgotten in the patch I
> sent.
> 
> Ludo’.

       reply	other threads:[~2019-01-11 14:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87fttz8mxu.fsf@gnu.org>
2019-01-11 14:02 ` ng0 [this message]
2019-01-13 20:55   ` bug#34020: [PATCH 0/2] Re-purpose '--verbosity' to something useful Ludovic Courtès
2019-01-13 21:01     ` ng0

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=E1ghxOe-0003Mp-EJ@rmmprod05.runbox \
    --to=ng0@n0.is \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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 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).