From: Junio C Hamano <gitster@pobox•com>
To: Elijah Newren <newren@gmail•com>
Cc: Git Mailing List <git@vger•kernel.org>
Subject: Re: ds/core-untrac[k]ed-cache-config
Date: Fri, 18 Feb 2022 08:50:40 -0800 [thread overview]
Message-ID: <xmqqbkz43yqn.fsf@gitster.g> (raw)
In-Reply-To: <CABPp-BEcUt-q4vXok=FqZSswPbdUT38=X3kUocbBKO5ydDPrQg@mail.gmail.com> (Elijah Newren's message of "Thu, 17 Feb 2022 21:19:40 -0800")
Elijah Newren <newren@gmail•com> writes:
> On Thu, Feb 17, 2022 at 5:34 PM Junio C Hamano <gitster@pobox•com> wrote:
>>
>> * ds/core-untraced-cache-config (2022-02-17) 1 commit
>> - dir: force untracked cache with core.untrackedCache
>>
>> Setting core.untrackedCache to true failed to add the untracked
>> cache extension to the index.
>>
>> Will merge to 'next'.
>> source: <pull.1058.v2.git.1645131630140.gitgitgadget@gmail•com>
>
> Any chance we could first rename the branch to insert a missing 'k'?
> 'untraced' and 'untracked' may only differ by a character, but their
> meaning differs a bit more...
Wow, embarrassing. Thanks.
next prev parent reply other threads:[~2022-02-18 16:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 1:13 What's cooking in git.git (Feb 2022, #05; Thu, 17) Junio C Hamano
2022-02-18 2:49 ` gc/recursive-fetch-with-unused-submodules (was Re: What's cooking in git.git (Feb 2022, #05; Thu, 17)) Glen Choo
2022-02-18 16:51 ` Junio C Hamano
2022-02-18 3:28 ` What's cooking in git.git (Feb 2022, #05; Thu, 17) Elijah Newren
2022-02-18 16:51 ` Junio C Hamano
2022-02-18 5:19 ` ds/core-untrac[k]ed-cache-config (Was: Re: What's cooking in git.git (Feb 2022, #05; Thu, 17)) Elijah Newren
2022-02-18 16:50 ` Junio C Hamano [this message]
2022-02-19 1:53 ` en/present-despite-skipped (Re: " Jonathan Nieder
2022-02-22 23:52 ` Jonathan Nieder
2022-02-23 19:39 ` Junio C Hamano
2022-02-25 16:43 ` Jonathan Nieder
2022-02-21 11:14 ` pw/single-key-interactive (was " Phillip Wood
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=xmqqbkz43yqn.fsf@gitster.g \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=newren@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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