From: Jeff Hostetler <Jeff.Hostetler@microsoft.com>
To: Junio C Hamano <gitster@pobox.com>,
Jeff Hostetler <git@jeffhostetler.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Jonathan Tan <jonathantanmy@google.com>,
"git@vger.kernel.org" <git@vger.kernel.org>,
"Jeff Hostetler" <Jeff.Hostetler@microsoft.com>
Subject: RE: What's cooking in git.git (Oct 2017, #07; Mon, 30)
Date: Tue, 31 Oct 2017 13:14:08 +0000 [thread overview]
Message-ID: <SN4PR2101MB07369D19A150418D5ACB858B8A5E0@SN4PR2101MB0736.namprd21.prod.outlook.com> (raw)
In-Reply-To: <xmqqtvyg2g6y.fsf@gitster.mtv.corp.google.com>
From: Junio C Hamano [mailto:gitster@pobox.com]
Subject: Re: What's cooking in git.git (Oct 2017, #07; Mon, 30)
> Jeff Hostetler <git@jeffhostetler.com> writes:
>
>> I've been assuming that the jt/partial-clone-lazy-fetch is a
>> placeholder for our next combined patch series.
>
> Yes, that, together with the expectation that I will hear from both you and JTan
> once the result of combined effort becomes ready to replace this placeholder,
> matches my assumption.
>
> Is that happening now?
Yes, I'm merging our them now and hope to have a version to
send to Jonathan and/or the list sometime this week.
Jeff
next prev parent reply other threads:[~2017-10-31 13:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 6:19 What's cooking in git.git (Oct 2017, #07; Mon, 30) Junio C Hamano
2017-10-30 12:40 ` Ben Peart
2017-10-30 17:24 ` Johannes Schindelin
2017-10-30 17:28 ` Johannes Schindelin
2017-10-31 2:38 ` Junio C Hamano
2017-10-31 17:18 ` Johannes Schindelin
2017-10-30 17:31 ` Johannes Schindelin
2017-10-30 19:54 ` Jeff Hostetler
2017-10-31 2:40 ` Junio C Hamano
2017-10-31 13:14 ` Jeff Hostetler [this message]
2017-11-01 1:21 ` Junio C Hamano
2017-11-01 17:58 ` Jonathan Tan
2017-11-02 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SN4PR2101MB07369D19A150418D5ACB858B8A5E0@SN4PR2101MB0736.namprd21.prod.outlook.com \
--to=jeff.hostetler@microsoft.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@jeffhostetler.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jonathantanmy@google.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).