From: Brandon Williams <bmwill@google.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jonathan Tan <jonathantanmy@google.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jul 2018, #02; Wed, 18)
Date: Tue, 24 Jul 2018 12:38:36 -0700 [thread overview]
Message-ID: <20180724193836.GD225275@google.com> (raw)
In-Reply-To: <xmqqd0vcxwfu.fsf@gitster-ct.c.googlers.com>
On 07/24, Junio C Hamano wrote:
> Jonathan Tan <jonathantanmy@google.com> writes:
>
> >> Here are the topics that have been cooking. Commits prefixed with
> >> '-' are only in 'pu' (proposed updates) while commits prefixed with
> >> '+' are in 'next'. The ones marked with '.' do not appear in any of
> >> the integration branches, but I am still holding onto them.
> >
> > What do you think about my fixes to protocol v2 tag following [1]? There
> > was some discussion about correctness vs the drop in performance, but it
> > seems to me that there is some consensus that the drop in performance is
> > OK.
> >
> > [1] https://public-inbox.org/git/cover.1528234587.git.jonathantanmy@google.com/
>
> Thanks for reminding. I think I was waiting for Brandon or somebody
> else to say something after [2] as the final confirmation before
> queuing it, and then the thread was forgotten ;-)
>
> Will pick it up; it seems to have some interaction with Brandon's
> 6d1700d5 ("fetch: refactor to make function args narrower",
> 2018-06-27), and I think the correct resolution is to move your
> removal of "&& !rs->nr" to do_fetch() function where that commit
> moved to.
>
> Thanks.
>
> [2] https://public-inbox.org/git/xmqqd0vwcfkr.fsf@gitster-ct.c.googlers.com/
Yeah I still don't like it from a performance perspective, but given
people rely on this functionality I've been convinced its necessary for
correctness until we make other changes.
--
Brandon Williams
prev parent reply other threads:[~2018-07-24 19:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 22:03 What's cooking in git.git (Jul 2018, #02; Wed, 18) Junio C Hamano
2018-07-18 23:41 ` Stefan Beller
2018-07-19 16:33 ` Junio C Hamano
2018-07-19 6:10 ` Оля Тележная
2018-07-19 8:48 ` Eric Sunshine
2018-07-19 16:36 ` Junio C Hamano
2018-07-19 17:10 ` Elijah Newren
2018-07-20 13:42 ` ds/multi-pack-index (was Re: What's cooking in git.git (Jul 2018, #02; Wed, 18)) Derrick Stolee
2018-07-20 16:09 ` Junio C Hamano
2018-07-20 16:28 ` Derrick Stolee
2018-07-20 17:48 ` ag/rebase-i-in-c, was Re: What's cooking in git.git (Jul 2018, #02; Wed, 18) Alban Gruin
2018-07-23 18:21 ` Jonathan Tan
2018-07-24 19:31 ` Junio C Hamano
2018-07-24 19:38 ` Brandon Williams [this message]
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=20180724193836.GD225275@google.com \
--to=bmwill@google.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.
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).