All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: Ravi Mistry <rmistry@google.com>,
	git@vger.kernel.org,
	"brian m. carlson" <sandals@crustytoothpaste.net>,
	Vaidas Pilkauskas <vaidas.pilkauskas@shopify.com>
Subject: Re: What's cooking in git.git (Nov 2026, #06)
Date: Wed, 18 Nov 2026 11:38:12 +0100	[thread overview]
Message-ID: <av2AFJ_WmUb0FGjU@pks.im> (raw)
In-Reply-To: <xmqqh5hgi9m3.fsf@gitster.g>

On Mon, Nov 16, 2026 at 04:29:08PM -0800, Junio C Hamano wrote:
> 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.

I'll bite and will send out a review in a bit.

Patrick

  reply	other threads:[~2026-11-18 10:38 UTC|newest]

Thread overview: 6+ 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
2026-11-18 10:38     ` Patrick Steinhardt [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=av2AFJ_WmUb0FGjU@pks.im \
    --to=ps@pks.im \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.