From: Victoria Dye <vdye@github.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Cc: 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 15:19:13 -0700 [thread overview]
Message-ID: <df61d79b-8234-d3fd-5eb5-614d1b97d046@github.com> (raw)
In-Reply-To: <xmqqo7ns69sz.fsf@gitster.g>
Junio C Hamano wrote:
> * rn/sparse-diff-index (2023-04-10) 1 commit
> - diff-index: enable sparse index
>
> "git diff-index" command has been taught to work better with the
> sparse index.
>
> Comments?
> source: <20230408112342.404318-1-nanth.raghul@gmail.com>
I just sent a review of the newest version [1] with some minor nits &
questions that may prompt a re-roll (depending on the author's/others'
thoughts).
[1] https://lore.kernel.org/git/62821012-4fc3-5ad8-695c-70f7ab14a8c9@github.com/
> * rn/sparse-describe (2023-04-03) 1 commit
> - describe: enable sparse index for describe
>
> "git describe --dirty" learns to work better with sparse-index.
>
> Will merge to 'next'?
> source: <20230403164749.246001-1-nanth.raghul@gmail.com>
This looks good to me, agreed that it's ready for 'next'.
> * sl/sparse-write-tree (2023-04-04) 1 commit
> (merged to 'next' on 2023-04-10 at 0cd39c23b1)
> + write-tree: integrate with sparse index
>
> "git write-tree" learns to work better with sparse-index.
>
> Will merge to 'master'.
> source: <20230404003539.1578245-1-cheskaqiqi@gmail.com>
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.
[2] https://lore.kernel.org/git/9d0309bd-943c-dd51-97cf-59721eda78f7@github.com/
> * 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], with similar nits &
questions to those in the 'diff-index' integration.
[3] https://lore.kernel.org/git/4ffff8e9-3e03-9c5f-4a42-b9102ed24e66@github.com/
[4] https://lore.kernel.org/git/c382017a-8c65-24ba-5092-6b46428d8b9b@github.com/
next prev parent reply other threads:[~2023-04-13 22:19 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 [this message]
2023-04-14 1:13 ` 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=df61d79b-8234-d3fd-5eb5-614d1b97d046@github.com \
--to=vdye@github.com \
--cc=cheskaqiqi@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nanth.raghul@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 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.