From: ludo@gnu.org (Ludovic Courtès)
To: Mathieu Lirzin <mthl@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 0/5] Automake custom test driver using SRFI-64.
Date: Fri, 01 Apr 2016 22:51:06 +0200 [thread overview]
Message-ID: <87fuv5kq85.fsf@gnu.org> (raw)
In-Reply-To: <1458776330-5005-1-git-send-email-mthl@gnu.org> (Mathieu Lirzin's message of "Thu, 24 Mar 2016 00:38:45 +0100")
Howdy!
Mathieu Lirzin <mthl@gnu.org> skribis:
> It is possible to directly checkout 'origin/wip-check' branch to review these
> patches. Thanks.
>
> Mathieu Lirzin (5):
> tests: Silence %cpio-program.
> build: Add a Guile custom test driver using SRFI-64.
> tests: Silence guix-daemon.
> tests: Silence %have-nix-hash?.
> tests: Silence tar.
I’m looking at it now. My first question is whether we could avoid
silencing everything?
I guess I got used to having an extra .log file containing “noise”, in
addition to the well-formatted .log file, and it’s proved useful on a
few occasions.
Cheers,
Ludo’.
next prev parent reply other threads:[~2016-04-01 20:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 23:38 [PATCH 0/5] Automake custom test driver using SRFI-64 Mathieu Lirzin
2016-03-23 23:38 ` [PATCH 1/5] tests: Silence %cpio-program Mathieu Lirzin
2016-03-23 23:38 ` [PATCH 2/5] build: Add a Guile custom test driver using SRFI-64 Mathieu Lirzin
2016-03-23 23:38 ` [PATCH 3/5] tests: Silence guix-daemon Mathieu Lirzin
2016-03-23 23:38 ` [PATCH 4/5] tests: Silence %have-nix-hash? Mathieu Lirzin
2016-03-23 23:38 ` [PATCH 5/5] tests: Silence tar Mathieu Lirzin
2016-03-24 4:15 ` [PATCH 0/5] Automake custom test driver using SRFI-64 Eric Bavier
2016-03-24 17:02 ` Mathieu Lirzin
2016-03-27 21:39 ` Ludovic Courtès
2016-03-27 21:47 ` Mathieu Lirzin
2016-04-01 20:51 ` Ludovic Courtès [this message]
2016-04-02 10:59 ` Mathieu Lirzin
2016-04-02 13:22 ` Ludovic Courtès
2016-04-02 14:25 ` Mathieu Lirzin
2016-04-03 12:33 ` Mathieu Lirzin
2016-04-03 21:30 ` Ludovic Courtès
2016-04-01 21:45 ` 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=87fuv5kq85.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mthl@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.