From: Jonathan Tan <jonathantanmy@google.com>
To: git@vger.kernel.org
Cc: Jonathan Tan <jonathantanmy@google.com>
Subject: [PATCH] do not reset in_vain on non-novel acks
Date: Thu, 22 Sep 2016 11:36:54 -0700 [thread overview]
Message-ID: <cover.1474568670.git.jonathantanmy@google.com> (raw)
This is regarding the packfile negotiation in fetch-pack. If there is a
concern that MAX_IN_VAIN would be hit too early (as a consequence of the
patch below), I'm currently investigating the possibility of improving
the negotiation ability of the client side further (for example, by
prioritizing refs or heads instead of merely prioritizing by date in the
priority queue of objects), but I thought I'd send the patch out first
anyway to see what others think.
Jonathan Tan (1):
fetch-pack: do not reset in_vain on non-novel acks
fetch-pack.c | 12 ++++++++++--
1 file changed, 10 insertions(+), 2 deletions(-)
--
2.8.0.rc3.226.g39d4020
next reply other threads:[~2016-09-22 18:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 18:36 Jonathan Tan [this message]
2016-09-22 18:36 ` [PATCH] fetch-pack: do not reset in_vain on non-novel acks Jonathan Tan
2016-09-22 20:05 ` Junio C Hamano
2016-09-23 17:41 ` [PATCH v2] " Jonathan Tan
2016-09-23 19:40 ` Junio C Hamano
2016-09-22 19:20 ` [PATCH] " 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=cover.1474568670.git.jonathantanmy@google.com \
--to=jonathantanmy@google.com \
--cc=git@vger.kernel.org \
/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).