all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: swedebugia@riseup.net
To: 27067@debbugs.gnu.org
Subject: bug#27067: Feature request: please allow for either automatic logging of all output of every guix commands or add an option to each guix command to allow it for all to be logged
Date: Mon, 17 Dec 2018 01:30:48 -0800	[thread overview]
Message-ID: <89638742053c32cc476eee3659f23131@riseup.net> (raw)
In-Reply-To: <CANb+58KETz3PuoLKTozBaqPCLXbmHkgDCP4ERiAnQ9Evxe4fYQ@mail.gmail.com>

Hi

I think the current logging is good enough.

I vote for closing this as Brenton did not answer during a long time and
nobody else thought this was worth implementing.

We could add a note to the manual with a very general pipe output tip,
but it would probably just clutter an already large manual.

-- 
Cheers 
Swedebugia

  parent reply	other threads:[~2018-12-17  9:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-25  7:54 bug#27067: Feature request: please allow for either automatic logging of all output of every guix commands or add an option to each guix command to allow it for all to be logged Brenton Horne
2017-05-25 16:41 ` Arun Isaac
2017-05-25 17:05 ` bug#27067: Reply to Arun Isaac's reply Brenton Horne
     [not found] ` <a7836b86.AEAAKjHnUF4AAAAAAAAAAAPE-g8AAAACwQwAAAAAAAW9WABZJwlc@mailjet.com>
     [not found]   ` <CANb+58K6AENjXCrPF=gE=ou+AKE=G+R9+qscPjj3vQjSE-eijQ@mail.gmail.com>
     [not found]     ` <3b96388e.AEAAKj4NjDIAAAAAAAAAAAPE-g8AAAACwQwAAAAAAAW9WABZJx4e@mailjet.com>
2017-05-25 18:25       ` bug#27067: Feature request: please allow for either automatic logging of all output of every guix commands or add an option to each guix command to allow it for all to be logged Brenton Horne
2017-05-25 20:10 ` Ricardo Wurmus
2017-05-25 20:33   ` Brenton Horne
2017-05-25 21:30     ` Ricardo Wurmus
2017-05-30 20:14 ` Ludovic Courtès
2018-12-17  9:30 ` swedebugia [this message]
2018-12-18 11:21   ` Ludovic Courtès

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=89638742053c32cc476eee3659f23131@riseup.net \
    --to=swedebugia@riseup.net \
    --cc=27067@debbugs.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.