From: Vincent Mailhol <mailhol@kernel.org>
To: Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>,
git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>,
Philippe Blain <levraiphilippeblain@gmail.com>,
Patrick Steinhardt <ps@pks.im>,
"D. Ben Knoble" <ben.knoble@gmail.com>
Subject: Re: [PATCH v3 0/4] completion: add support for 'git history'
Date: Fri, 14 Aug 2026 08:25:17 +0200 [thread overview]
Message-ID: <3d0e8944-c17b-4665-88e0-2f955d52e8e9@kernel.org> (raw)
In-Reply-To: <bd3707a8-70ad-4308-bc93-5aad84e028d6@app.fastmail.com>
On 13/08/2026 at 22:30, Kristoffer Haugsbakk wrote:
> On Thu, Aug 13, 2026, at 21:05, Vincent Mailhol wrote:
>> This series adds Bash completion for the subcommands of "git history"
>> and their options.
>>
>> Patch #1 adds the basic subcommand and options completion. Patch #2 and
>>
>> options. Finally, Patch #4 adds completion for pathspecs accepted by
>> "split".
>
> It looks like one line was accidentally deleted/blanked. But I think
> it would say the same thing as on v2:
>
> ---
> Patch #1 adds the basic subcommand and options completion. Patch #2
> and #3 take care of the value of the --empty and --update-refs options.
> Finally, Patch #4 adds completion for pathspecs accepted by "split".
> ---
>
> Was the paragraph reflowed with
> "#3" at the start and treated like
> a comment line?
Exactly.
This is the cover letter as I intended to send it:
completion: add support for 'git history'
This series adds Bash completion for the subcommands of "git history"
and their options.
Patch #1 adds the basic subcommand and options completion. Patch #2 and
#3 take care of, respectively, the value of the --empty and --update-refs
options. Finally, Patch #4 adds completion for pathspecs accepted by
"split".
For each of the completions, add a set of relevant test cases.
As you guessed, b4 removed the line starting with #3. I didn't see this
coming. From now on, I will stop using # in the description.
Should I send a v4 with the fixed cover letter, or is it OK as-is?
Yours sincerely,
Vincent Mailhol
next prev parent reply other threads:[~2026-08-14 6:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 19:56 [PATCH] completion: add 'git history' subcommands Vincent Mailhol
2026-08-05 6:19 ` Patrick Steinhardt
2026-08-05 11:56 ` D. Ben Knoble
2026-08-05 16:15 ` Junio C Hamano
2026-08-05 21:20 ` Vincent Mailhol
2026-08-06 5:18 ` Patrick Steinhardt
2026-08-13 19:05 ` [PATCH v3 0/4] completion: add support for 'git history' Vincent Mailhol
2026-08-13 19:05 ` [PATCH v3 1/4] completion: add 'git history' subcommands Vincent Mailhol
2026-08-19 11:13 ` Patrick Steinhardt
2026-08-13 19:05 ` [PATCH v3 2/4] completion: complete 'git history --empty' values Vincent Mailhol
2026-08-19 11:13 ` Patrick Steinhardt
2026-08-13 19:05 ` [PATCH v3 3/4] completion: complete 'git history --update-refs' values Vincent Mailhol
2026-08-13 19:05 ` [PATCH v3 4/4] completion: complete 'git history split' pathspecs Vincent Mailhol
2026-08-13 20:30 ` [PATCH v3 0/4] completion: add support for 'git history' Kristoffer Haugsbakk
2026-08-14 6:25 ` Vincent Mailhol [this message]
2026-08-14 7:50 ` Kristoffer Haugsbakk
2026-08-19 11:13 ` Patrick Steinhardt
2026-08-19 20:18 ` Junio C Hamano
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=3d0e8944-c17b-4665-88e0-2f955d52e8e9@kernel.org \
--to=mailhol@kernel.org \
--cc=ben.knoble@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kristofferhaugsbakk@fastmail.com \
--cc=levraiphilippeblain@gmail.com \
--cc=ps@pks.im \
/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.