From: ludo@gnu.org (Ludovic Courtès)
To: 33161-done@debbugs.gnu.org
Subject: bug#33161: [PATCH 0/1] Add 'guix processes'
Date: Mon, 29 Oct 2018 00:15:09 +0100 [thread overview]
Message-ID: <87pnvt3bpe.fsf@gnu.org> (raw)
In-Reply-To: <20181026092512.28810-1-ludo@gnu.org> ("Ludovic \=\?utf-8\?Q\?Cou\?\= \=\?utf-8\?Q\?rt\=C3\=A8s\=22's\?\= message of "Fri, 26 Oct 2018 11:25:12 +0200")
Ludovic Courtès <ludo@gnu.org> skribis:
> This patch adds a ‘guix processes’ command that I find handy to
> inspect/debug Guix activity. In particular, I realized I had been
> doing this by hand on berlin when trying to understand what’s going
> on, so this tool will be helpful there. :-)
Pushed as 63eb2b899be7ac857454442e09d0ebd23fe4f871 with small
improvements to the doc!
Ludo’.
prev parent reply other threads:[~2018-10-28 23:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 9:25 [bug#33161] [PATCH 0/1] Add 'guix processes' Ludovic Courtès
2018-10-26 9:42 ` [bug#33161] [PATCH 1/1] " Ludovic Courtès
2018-10-28 23:15 ` Ludovic Courtès [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=87pnvt3bpe.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=33161-done@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 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).