From: "Ludovic Courtès" <ludo@gnu.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: 43261@debbugs.gnu.org, zimoun <zimon.toutoune@gmail.com>
Subject: [bug#43261] [PATCH 0/2] lint: Fix 'no-network' and add 'no-checkers' options
Date: Wed, 28 Oct 2020 16:13:59 +0100 [thread overview]
Message-ID: <87h7qe1iyw.fsf@gnu.org> (raw)
In-Reply-To: <20200908075636.GF1643@E5400> (Efraim Flashner's message of "Tue, 8 Sep 2020 10:56:36 +0300")
Hi,
Efraim Flashner <efraim@flashner.co.il> skribis:
> On Mon, Sep 07, 2020 at 08:02:29PM +0200, zimoun wrote:
[...]
>> The second patch adds the '--no-checkers' option discussed some time ago. I
>> am not convinced by the 'option-checker' helper function. What could be
>> better?
>>
>> Instead of '--no-checkers' maybe '--exclude-checkers' is a better name.
>>
>
> how about '--skip'
I’d suggest ‘--exclude’ + ‘-x’, which is similar to what ‘guix hash’
does for instance.
Ludo’.
next prev parent reply other threads:[~2020-10-28 15:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 18:02 [bug#43261] [PATCH 0/2] lint: Fix 'no-network' and add 'no-checkers' options zimoun
2020-09-07 18:04 ` [bug#43261] [PATCH 1/2] lint: Fix '--no-network' option zimoun
2020-09-07 18:04 ` [bug#43261] [PATCH 2/2] lint: Add '--no-checkers' option zimoun
2020-10-28 15:18 ` Ludovic Courtès
2020-10-28 16:58 ` zimoun
2020-09-08 7:56 ` [bug#43261] [PATCH 0/2] lint: Fix 'no-network' and add 'no-checkers' options Efraim Flashner
2020-09-08 9:16 ` zimoun
2020-10-28 15:13 ` Ludovic Courtès [this message]
2020-10-09 20:39 ` zimoun
2020-10-28 16:51 ` [bug#43261] [PATCH v2 1/2] scripts: lint: Fix '--no-network' option zimoun
2020-10-28 16:51 ` [bug#43261] [PATCH v2 2/2] scripts: lint: Add '--exclude' option zimoun
2020-10-29 23:28 ` bug#43261: " Ludovic Courtès
2020-10-29 23:25 ` [bug#43261] [PATCH v2 1/2] scripts: lint: Fix '--no-network' option 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
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=87h7qe1iyw.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=43261@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=zimon.toutoune@gmail.com \
/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).