From: Junio C Hamano <gitster@pobox•com>
To: Shuqi Liang <cheskaqiqi@gmail•com>
Cc: Victoria Dye <vdye@github•com>,
git@vger•kernel.org, Derrick Stolee <derrickstolee@github•com>
Subject: Re: [PATCH v3] write-tree: integrate with sparse index
Date: Thu, 20 Apr 2023 08:55:34 -0700 [thread overview]
Message-ID: <xmqqleim4kg9.fsf@gitster.g> (raw)
In-Reply-To: <CAMO4yUGzGzT4XC8t_LE=Z=ebERJq9Egq+wFj1K=1aUxHfPcnNA@mail.gmail.com> (Shuqi Liang's message of "Thu, 20 Apr 2023 01:24:18 -0400")
Shuqi Liang <cheskaqiqi@gmail•com> writes:
>> Sorry, but after this exchange
>>
>> https://lore.kernel.org/git/xmqqmt3bw9ir.fsf@gitster.g/
>>
>> I am confused what we want to do with this version.
>
> Apologies for not noticing the patch was already merged to master. I'll make
> the necessary changes and submit a new patch soon.
No need to apologize. I should have been able to guess what happend
myself.
Thanks for offering to make your updates incremental. Will look
forward to seeing them.
next prev parent reply other threads:[~2023-04-20 15:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-02 0:01 [RFC][PATCH v1] write-tree: integrate with sparse index Shuqi Liang
2023-04-03 20:58 ` Junio C Hamano
2023-04-03 22:16 ` Shuqi Liang
2023-04-03 22:54 ` Junio C Hamano
2023-04-04 0:35 ` [PATCH v2] " Shuqi Liang
2023-04-05 17:31 ` Victoria Dye
2023-04-05 19:48 ` Junio C Hamano
2023-04-19 7:21 ` [PATCH v3] " Shuqi Liang
2023-04-19 15:47 ` Junio C Hamano
2023-04-20 5:24 ` Shuqi Liang
2023-04-20 15:55 ` Junio C Hamano [this message]
2023-04-21 0:41 ` [PATCH v4] " Shuqi Liang
2023-04-21 21:42 ` Victoria Dye
2023-04-24 15:14 ` Junio C Hamano
2023-04-23 7:12 ` [PATCH v5] write-tree: optimize sparse integration Shuqi Liang
2023-04-24 16:00 ` Junio C Hamano
2023-05-08 20:05 ` [PATCH v6] " Shuqi Liang
2023-05-08 20:21 ` Shuqi Liang
2023-05-08 21:09 ` Junio C Hamano
2023-05-08 21:27 ` Shuqi Liang
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=xmqqleim4kg9.fsf@gitster.g \
--to=gitster@pobox$(echo .)com \
--cc=cheskaqiqi@gmail$(echo .)com \
--cc=derrickstolee@github$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=vdye@github$(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