From: Derrick Stolee <stolee@gmail.com>
To: Elijah Newren <newren@gmail.com>, Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Jonathan Tan <jonathantanmy@google.com>
Subject: Re: What's cooking in git.git (Jul 2021, #01; Tue, 6)
Date: Thu, 8 Jul 2021 08:39:24 -0400 [thread overview]
Message-ID: <8756d446-b191-ac7e-9eff-5c0ea040e582@gmail.com> (raw)
In-Reply-To: <CABPp-BGt0E4nLtU6Ocn0dUwOUUwDkz-90KKUpSLK9ctU9tQXmA@mail.gmail.com>
On 7/6/21 9:46 PM, Elijah Newren wrote:
> On Tue, Jul 6, 2021 at 6:20 PM Junio C Hamano <gitster@pobox.com> wrote:
>
>> * ds/commit-and-checkout-with-sparse-index (2021-06-28) 5 commits
...>
> This was submitted at the same time as the latest round of
> ds/status-with-sparse-index. Last week was a bit busy for me. I'd
> like to complete reviewing the latest round from the other series,
> then I'll review this one. So I'll have some comments soon-ish (by
> end of week).
>
>> * ds/status-with-sparse-index (2021-06-28) 16 commits
...
>
> Sorry for the delay. I reviewed about half of the latest round last
> week, and it appears all my feedback from earlier rounds was addressed
> from what I've seen so far. I suspect this series is now good to go
> and I'd like to stick my Reviewed-by on it before it goes to next, but
> I need to complete my review first. I should be able to complete it
> by end of week.
I appreciate your attention to these contributions. I have also
had a significant lack of time the past few weeks and hopefully
will be able to spend more time on-list starting the 19th.
-Stolee
next prev parent reply other threads:[~2021-07-08 12:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 1:19 What's cooking in git.git (Jul 2021, #01; Tue, 6) Junio C Hamano
2021-07-07 1:46 ` Elijah Newren
2021-07-08 12:39 ` Derrick Stolee [this message]
2021-07-07 2:35 ` Felipe Contreras
2021-07-07 5:54 ` Atharva Raykar
2021-07-07 19:38 ` Eric Wong
2021-07-07 23:08 ` Philippe Blain
2021-07-08 0:18 ` 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=8756d446-b191-ac7e-9eff-5c0ea040e582@gmail.com \
--to=stolee@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jonathantanmy@google.com \
--cc=newren@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 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).