git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jonathan Tan <jonathantanmy@google.com>
To: gitster@pobox.com
Cc: git@vger.kernel.org, Jonathan Tan <jonathantanmy@google.com>
Subject: Re: What's cooking in git.git (Jul 2018, #02; Wed, 18)
Date: Mon, 23 Jul 2018 11:21:49 -0700	[thread overview]
Message-ID: <20180723182149.202859-1-jonathantanmy@google.com> (raw)
In-Reply-To: <xmqqtvowi4l3.fsf@gitster-ct.c.googlers.com>

> 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/

  parent reply	other threads:[~2018-07-23 18:21 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 [this message]
2018-07-24 19:31   ` Junio C Hamano
2018-07-24 19:38     ` Brandon Williams

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=20180723182149.202859-1-jonathantanmy@google.com \
    --to=jonathantanmy@google.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).