From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 47464-done@debbugs.gnu.org
Subject: bug#47464: [PATCH 0/8] scripts: Allow option hint for various subcommands.
Date: Thu, 01 Apr 2021 14:57:27 +0200 [thread overview]
Message-ID: <87k0pm88nc.fsf@gnu.org> (raw)
In-Reply-To: <20210329101638.53217-1-zimon.toutoune@gmail.com> (zimoun's message of "Mon, 29 Mar 2021 12:16:38 +0200")
Hi!
zimoun <zimon.toutoune@gmail.com> skribis:
> The patch set replaces all the 'args-fold*' by 'parse-command-line'. Doing
> so, all the option typos are hinted.
Yay!
> It could be only one commit (squashing) but it appeared me easier in case
> something is wrong; I expect nothing! :-)
>
> I have checked trying various combinations. Note that
> "tests/guix-describe.sh" is SKIP because the test does not work when using
> worktree.
>
> Well, a double-check is really welcome. :-)
All the tests pass, LGTM!
> All the remaining subcommands---authenticate, container, git, import, offload
> and substitute---needs a rewriting of how they parse the command line
> arguments.
Future work.
Applied, thanks!
Ludo’.
prev parent reply other threads:[~2021-04-01 13:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 10:16 [bug#47464] [PATCH 0/8] scripts: Allow option hint for various subcommands zimoun
2021-03-29 10:17 ` [bug#47464] [PATCH 1/8] scripts: describe: Replace 'args-fold*' by 'parse-command-line' zimoun
2021-03-29 10:18 ` [bug#47464] [PATCH 2/8] scripts: discover: " zimoun
2021-03-29 10:18 ` [bug#47464] [PATCH 3/8] scripts: download: " zimoun
2021-03-29 10:18 ` [bug#47464] [PATCH 4/8] scripts: edit: " zimoun
2021-03-29 10:18 ` [bug#47464] [PATCH 5/8] scripts: publish: " zimoun
2021-03-29 10:18 ` [bug#47464] [PATCH 6/8] scripts: repl: " zimoun
2021-03-29 10:18 ` [bug#47464] [PATCH 7/8] scripts: search: " zimoun
2021-03-29 10:18 ` [bug#47464] [PATCH 8/8] scripts: show: " zimoun
2021-04-01 12:57 ` 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=87k0pm88nc.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=47464-done@debbugs.gnu.org \
--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).