From: Junio C Hamano <gitster@pobox.com>
To: Victoria Dye <vdye@github.com>
Cc: git@vger.kernel.org, Raghul Nanth A <nanth.raghul@gmail.com>,
Shuqi Liang <cheskaqiqi@gmail.com>
Subject: Re: What's cooking in git.git (Apr 2023, #03; Tue, 11)
Date: Thu, 13 Apr 2023 18:13:48 -0700 [thread overview]
Message-ID: <xmqqmt3bw9ir.fsf@gitster.g> (raw)
In-Reply-To: <df61d79b-8234-d3fd-5eb5-614d1b97d046@github.com> (Victoria Dye's message of "Thu, 13 Apr 2023 15:19:13 -0700")
Victoria Dye <vdye@github.com> writes:
> Junio C Hamano wrote:
>> * rn/sparse-diff-index (2023-04-10) 1 commit
> ...
> I just sent a review of the newest version [1] ...
Thanks.
>> * rn/sparse-describe (2023-04-03) 1 commit
>> - describe: enable sparse index for describe
>> ...
> This looks good to me, agreed that it's ready for 'next'.
Yeah, thanks for helping the author to polish the topic into a very
good shape.
>> * sl/sparse-write-tree (2023-04-04) 1 commit
> ...
> Sorry for getting to this one so late - I did have some comments [2] on the
> tests in this patch that weren't addressed. However, I'm fairly certain the
> integration itself is correct, so I may just submit the test updates as a
> separate patch in the (near-ish?) future.
Again, very much appreciated.
>> * sl/diff-files-sparse (2023-03-22) 2 commits
>> - diff-files: integrate with sparse index
>> - t1092: add tests for `git diff-files`
>>
>> Teach "diff-files" not to expand sparse-index unless needed.
>>
>> Comments?
>> source: <20230322161820.3609-1-cheskaqiqi@gmail.com>
>
> I also just sent a review for this one [3] [4], ...
Yup, I saw them. Looked very sensible.
Thanks.
prev parent reply other threads:[~2023-04-14 1:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 21:59 What's cooking in git.git (Apr 2023, #03; Tue, 11) Junio C Hamano
2023-04-12 22:04 ` Taylor Blau
2023-04-13 0:24 ` Andrei Rybak
2023-04-13 15:06 ` Junio C Hamano
2023-04-13 22:19 ` Victoria Dye
2023-04-14 1:13 ` 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=xmqqmt3bw9ir.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=cheskaqiqi@gmail.com \
--cc=git@vger.kernel.org \
--cc=nanth.raghul@gmail.com \
--cc=vdye@github.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 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.