From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Derrick Stolee <dstolee@microsoft.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (May 2019, #04; Tue, 28)
Date: Wed, 29 May 2019 09:53:44 -0700 [thread overview]
Message-ID: <xmqqlfypyzfr.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20190528222604.GA14921@sigill.intra.peff.net> (Jeff King's message of "Tue, 28 May 2019 18:26:04 -0400")
Jeff King <peff@peff.net> writes:
> On Tue, May 28, 2019 at 03:08:31PM -0700, Junio C Hamano wrote:
>
>> Quite a few new topics, most of which are fixes with different
>> urgency, have been picked up. Perhaps we'd need an extra -rc for
>> this cycle to squash existing regression at the tip of 'master'.
>> At this point, the criteria for merging to 'master' is *NOT* "This
>> is an obviously correct fix", but is "This is an obviously correct
>> fix for a breakage we introduced during this cycle".
>>
>> [...]
>>
>> * ds/object-info-for-prefetch-fix (2019-05-28) 1 commit
>> - sha1-file: split OBJECT_INFO_FOR_PREFETCH
>>
>> Code cleanup.
>>
>> Will merge to 'next'.
>
> I think this one is actually a bug-fix (we are refusing to prefetch for
> "QUICK" calls even though was not the intent), and it is new in this
> release.
>
> I'm not sure of the user-visible impacts, though. There are a lot of
> QUICK calls, and I'm not sure for which ones it is important to fetch.
Hmph. I took it as primarily futureproofing, as I didn't find a way
to trigger bad behaviour from within the current codebase.
next prev parent reply other threads:[~2019-05-29 16:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 22:08 What's cooking in git.git (May 2019, #04; Tue, 28) Junio C Hamano
2019-05-28 22:26 ` Jeff King
2019-05-29 16:53 ` Junio C Hamano [this message]
2019-05-30 11:51 ` Jeff King
2019-05-30 15:01 ` Johannes Schindelin
2019-05-30 18:29 ` Derrick Stolee
2019-05-29 12:26 ` ab/send-email-transferencoding-fix, was " Johannes Schindelin
2019-05-29 12:36 ` Ævar Arnfjörð Bjarmason
2019-05-29 17:31 ` Junio C Hamano
2019-05-29 18:10 ` Johannes Schindelin
2019-05-29 19:54 ` 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=xmqqlfypyzfr.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=dstolee@microsoft.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).