From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS31976 209.132.180.0/23 X-Spam-Status: No, score=-4.0 required=3.0 tests=AWL,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_NONE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by dcvr.yhbt.net (Postfix) with ESMTP id D3AEA1F609 for ; Tue, 28 May 2019 22:26:12 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726990AbfE1W0L (ORCPT ); Tue, 28 May 2019 18:26:11 -0400 Received: from cloud.peff.net ([104.130.231.41]:40592 "HELO cloud.peff.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1726910AbfE1W0L (ORCPT ); Tue, 28 May 2019 18:26:11 -0400 Received: (qmail 7363 invoked by uid 109); 28 May 2019 22:26:11 -0000 Received: from Unknown (HELO peff.net) (10.0.1.2) by cloud.peff.net (qpsmtpd/0.94) with SMTP; Tue, 28 May 2019 22:26:11 +0000 Authentication-Results: cloud.peff.net; auth=none Received: (qmail 19623 invoked by uid 111); 28 May 2019 22:26:48 -0000 Received: from sigill.intra.peff.net (HELO sigill.intra.peff.net) (10.0.0.7) by peff.net (qpsmtpd/0.94) with (ECDHE-RSA-AES256-GCM-SHA384 encrypted) SMTP; Tue, 28 May 2019 18:26:48 -0400 Authentication-Results: peff.net; auth=none Received: by sigill.intra.peff.net (sSMTP sendmail emulation); Tue, 28 May 2019 18:26:04 -0400 Date: Tue, 28 May 2019 18:26:04 -0400 From: Jeff King To: Junio C Hamano Cc: Derrick Stolee , git@vger.kernel.org Subject: Re: What's cooking in git.git (May 2019, #04; Tue, 28) Message-ID: <20190528222604.GA14921@sigill.intra.peff.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org 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. -Peff