Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Ravi Mistry <rmistry@google.com>
Cc: git@vger.kernel.org,
	 "brian m. carlson" <sandals@crustytoothpaste.net>,
	Vaidas Pilkauskas <vaidas.pilkauskas@shopify.com>,
	 Patrick Steinhardt <ps@pks.im>
Subject: Re: What's cooking in git.git (Nov 2026, #06)
Date: Mon, 16 Nov 2026 16:29:08 -0800	[thread overview]
Message-ID: <xmqqh5hgi9m3.fsf@gitster.g> (raw)
In-Reply-To: <CAF+mdicGt4+aydaTqjP1DJRzxpRBbKSQQNai7BvXepC5Kt1vVg@mail.gmail.com> (Ravi Mistry's message of "Mon, 16 Nov 2026 13:09:29 -0800")

Ravi Mistry <rmistry@google.com> writes:

> Junio C Hamano <gitster@pobox.com> writes:
>
>> * rm/http-retry-improvements (2026-11-06) 5 commits
>>  - http: default http.retryAfter to 10 seconds
>>  - remote-curl: retry transient HTTP errors in post_rpc()
>>  - http: add http.retryStatusCodes config option
>>  - http: add exponential backoff without Retry-After
>>  - http: fix retry count and Retry-After timing
>> ...
>>  Needs review.
>
> Since there have been no further comments on v3, does this look ready
> for 'next' as is, or would you like me to send a v4 folding 5/5 into
> Patch 2?

I am reasonably happy with the series as-is.  My eyes were staring
these patches for too long and I would prefer to see somebody else
give a second opinion review, even a cursory one, though.

  reply	other threads:[~2026-11-17  0:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-16 15:15 What's cooking in git.git (Nov 2026, #06) Junio C Hamano
2026-11-16 21:09 ` Ravi Mistry
2026-11-17  0:29   ` Junio C Hamano [this message]
2026-11-17 16:46 ` Adrian Ratiu
2026-11-17 20:07   ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqh5hgi9m3.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=ps@pks.im \
    --cc=rmistry@google.com \
    --cc=sandals@crustytoothpaste.net \
    --cc=vaidas.pilkauskas@shopify.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