From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jul 2026, #09)
Date: Wed, 22 Jul 2026 11:27:55 -0700 [thread overview]
Message-ID: <xmqqzeziop5g.fsf@gitster.g> (raw)
In-Reply-To: <CAP8UFD3qTPak-RGtJ6cG7JkvX3_NZGHUB9N+rQk8ea2S_MDssA@mail.gmail.com> (Christian Couder's message of "Wed, 22 Jul 2026 11:02:52 +0200")
Christian Couder <christian.couder@gmail.com> writes:
>> * cc/fast-import-usage (2026-07-16) 7 commits
>> - fast-import: use struct option for usage string
>> - fast-import: move command state globals into 'struct fast_import_state'
>> - fast-import: introduce 'struct fast_import_state'
>> - fast-import: localize 'i' into the 'for' loops using it
>> - api-parse-options.adoc: document hidden and OPT_*_F option macros
>> - api-parse-options.adoc: document per-option flags
>> - parse-options: introduce OPT_HIDDEN_GROUP
>>
>> The usage string of 'git fast-import' has been updated to use the
>> 'parse_options' API for displaying help, and its SYNOPSIS in the
>> documentation has been standardized to match.
>>
>> Waiting for response.
>> cf. <xmqq4ihyehyb.fsf@gitster.g>
>> source: <20260716165517.433849-1-christian.couder@gmail.com>
>
> I am having a vacation, so I will likely not be able to reply soon.
> Feel free to discard in the meantime.
I'll leave it as-is (unless somebody else comes in and crashes with
the changes in the topic badly, in which case I may eject one or the
other from my tree). Enjoy your vacation.
Thanks.
prev parent reply other threads:[~2026-07-22 18:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 2:19 What's cooking in git.git (Jul 2026, #09) Junio C Hamano
2026-07-22 9:02 ` Christian Couder
2026-07-22 18:27 ` Junio C Hamano [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqzeziop5g.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox