From: Derrick Stolee <derrickstolee@github.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2023, #02; Tue, 6)
Date: Tue, 6 Jun 2023 09:35:01 -0400 [thread overview]
Message-ID: <e08f5cea-67dc-6b96-098f-118934c11b6d@github.com> (raw)
In-Reply-To: <xmqq5y814aw8.fsf@gitster.g>
On 6/5/2023 9:50 PM, Junio C Hamano wrote:
> * ds/add-i-color-configuration-fix (2023-06-06) 1 commit
> - add: check color.ui for interactive add
>
> The reimplemented "git add -i" did not honor color.ui configuration.
>
> Will merge to 'next'?
> source: <pull.1541.git.1685994164018.gitgitgadget@gmail.com>
Your recommendation to compare the raw output to the color-decoded output
is a clean way to simplify the test (and remove the whitespace errors in
the meantime). I'll send a v2 soon with that change.
> * ds/disable-replace-refs (2023-06-03) 3 commits
> - repository: create read_replace_refs setting
> - replace-objects: create wrapper around setting
> - repository: create disable_replace_refs()
> (this branch uses tb/pack-bitmap-traversal-with-boundary.)
>
> Introduce a mechanism to disable replace refs globally and per
> repository.
>
> Will merge to 'next'.
> source: <pull.1537.v2.git.1685716157.gitgitgadget@gmail.com>
Please be sure to pick up v3 [1], which fixes a compilation bug in
v2's patch 2. Want to keep history bisectable.
[1] https://lore.kernel.org/git/pull.1537.v3.git.1686057877.gitgitgadget@gmail.com
Thanks,
-Stolee
next prev parent reply other threads:[~2023-06-06 13:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 1:50 What's cooking in git.git (Jun 2023, #02; Tue, 6) Junio C Hamano
2023-06-06 9:15 ` Kristoffer Haugsbakk
2023-06-12 17:53 ` Junio C Hamano
2023-06-06 13:35 ` Derrick Stolee [this message]
2023-06-12 17:55 ` Junio C Hamano
2023-06-11 15:15 ` Philippe Blain
2023-06-12 17:56 ` 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=e08f5cea-67dc-6b96-098f-118934c11b6d@github.com \
--to=derrickstolee@github.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 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).