From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: ab/align-parse-options-help & ab/help-config-vars
Date: Fri, 01 Oct 2021 17:01:38 +0200 [thread overview]
Message-ID: <87a6jsrdj0.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqh7e18soj.fsf@gitster.g>
On Thu, Sep 30 2021, Junio C Hamano wrote:
> * ab/align-parse-options-help (2021-09-22) 4 commits
> - parse-options: properly align continued usage output
> - git rev-parse --parseopt tests: add more usagestr tests
> - send-pack: properly use parse_options() API for usage string
> - parse-options API users: align usage output in C-strings
>
> When "git cmd -h" shows more than one line of usage text (e.g.
> the cmd subcommand may take sub-sub-command), parse-options API
> learned to align these lines, even across i18n/l10n.
>
> Will merge to 'next'?
>
>
> * ab/help-config-vars (2021-09-23) 9 commits
> - help: move column config discovery to help.c library
> - help / completion: make "git help" do the hard work
> - help tests: test --config-for-completion option & output
> - help: simplify by moving to OPT_CMDMODE()
> - help: correct logic error in combining --all and --guides
> - help: correct logic error in combining --all and --config
> - help tests: add test for --config output
> - help: correct usage & behavior of "git help --guides"
> - help: correct the usage string in -h and documentation
>
> Teach "git help -c" into helping the command line completion of
> configuration variables.
>
> Will merge to 'next'?
I think the v5[1] and v3[2] of these have, respectively, reached an
"addressed all feedback" and "should be good enough". I.e. had some
feedback on [2] that I'm choosing to read as some post-cleanup
suggestions :)
The reason I wanted [2] was for some user-facing documentation query
improvements in "git help", so having it go forward would be
great. Thanks!
1. https://lore.kernel.org/git/cover-v5-0.4-00000000000-20210921T132350Z-avarab@gmail.com/
2. https://lore.kernel.org/git/cover-v3-0.9-00000000000-20210921T223223Z-avarab@gmail.com/
next prev parent reply other threads:[~2021-10-01 15:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 1:01 What's cooking in git.git (Sep 2021, #09; Thu, 30) Junio C Hamano
2021-10-01 6:20 ` en/removing-untracked-fixes [Was: Re: What's cooking in git.git (Sep 2021, #09; Thu, 30)] Elijah Newren
2021-10-01 8:51 ` Ævar Arnfjörð Bjarmason
2021-10-01 17:05 ` en/removing-untracked-fixes [ Junio C Hamano
2021-10-01 6:31 ` en/remerge-diff [Was: Re: What's cooking in git.git (Sep 2021, #09; Thu, 30)] Elijah Newren
2021-10-01 7:01 ` Jeff King
2021-10-01 12:05 ` What's cooking in git.git (Sep 2021, #09; Thu, 30) Ævar Arnfjörð Bjarmason
2021-10-01 12:08 ` ab/fsck-unexpected-type Ævar Arnfjörð Bjarmason
2021-10-01 14:32 ` ab/parse-options-cleanup Ævar Arnfjörð Bjarmason
2021-10-01 14:35 ` ab/sanitize-leak-ci & more leak fixes soon-or-not Ævar Arnfjörð Bjarmason
2021-10-01 14:48 ` ab/refs-errno-cleanup Ævar Arnfjörð Bjarmason
2021-10-01 14:56 ` What's cooking in git.git (Sep 2021, #09; Thu, 30) Jeff Hostetler
2021-10-01 15:01 ` Ævar Arnfjörð Bjarmason [this message]
2021-10-01 15:05 ` ab/lib-subtest Ævar Arnfjörð Bjarmason
2021-10-01 15:07 ` ab/config-based-hooks-1 Ævar Arnfjörð Bjarmason
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=87a6jsrdj0.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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.