From: Junio C Hamano <gitster@pobox.com>
To: "D. Ben Knoble" <ben.knoble@gmail.com>
Cc: git@vger.kernel.org, Phillip Wood <phillip.wood123@gmail.com>,
Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Subject: Re: What's cooking in git.git (Oct 2025, #04; Fri, 10)
Date: Sat, 11 Oct 2025 10:14:14 -0700 [thread overview]
Message-ID: <xmqqa51x7449.fsf@gitster.g> (raw)
In-Reply-To: <CALnO6CBEfzeSDRcVOR5chsHUSj1eM7RvTFJOVZ1h0X7Sqbaj=g@mail.gmail.com> (D. Ben Knoble's message of "Sat, 11 Oct 2025 10:35:09 -0400")
"D. Ben Knoble" <ben.knoble@gmail.com> writes:
> On Fri, Oct 10, 2025 at 8:00 PM Junio C Hamano <gitster@pobox.com> wrote:
>> --------------------------------------------------
>> [New Topics]
>>
>> * dk/stash-apply-index (2025-10-06) 1 commit
>> - doc: explain the impact of stash.index on --autostash options
>>
>> Doc update.
>>
>> Will merge to 'next'.
>> source: <d4a277b6b0695d86636562f4c07efae17f9249f9.1759755379.git.ben.knoble+github@gmail.com>
>
> I think Kristoffer had some feedback about the message—if changes need
> made, my understanding is that happens prior to "next" ?
>
> I'll send a reply there shortly, at any rate.
OK, will wait (I am not sure what needs updated, though).
>> * jc/optional-path (2025-09-28) 4 commits
>> (merged to 'next' on 2025-10-08 at a1e8af9952)
>> + parseopt: values of pathname type can be prefixed with :(optional)
>> + config: values of pathname type can be prefixed with :(optional)
>> + t7500: fix GIT_EDITOR shell snippet
>> + t7500: make each piece more independent
>>
>> Configuration variables that take a pathname as a value
>> (e.g. blame.ignorerevsfile) can be marked as optional by prefixing
>> ":(optoinal)" before its value.
>>
>> Will merge to 'master'.
>> source: <cover.1759094936.git.ben.knoble+github@gmail.com>
>
> As I mentioned in <1D9EE7CD-800B-4B70-8D98-79B0C2FB8DBA@gmail.com>, I
> think we might want a slight reroll for some tests and to use the
> correct functions in a few places.
If you want to change anything, can you do it with incremental
patches on top? Thanks.
next prev parent reply other threads:[~2025-10-11 17:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-11 0:00 What's cooking in git.git (Oct 2025, #04; Fri, 10) Junio C Hamano
2025-10-11 5:23 ` Eric Sunshine
2025-10-13 15:28 ` Junio C Hamano
2025-10-11 11:00 ` Patrick Steinhardt
2025-10-13 14:07 ` Junio C Hamano
2025-10-11 14:35 ` D. Ben Knoble
2025-10-11 17:14 ` Junio C Hamano [this message]
2025-10-12 18:02 ` Ben Knoble
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=xmqqa51x7449.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=ben.knoble@gmail.com \
--cc=git@vger.kernel.org \
--cc=kristofferhaugsbakk@fastmail.com \
--cc=phillip.wood123@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.
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 NNTP newsgroup(s).