On Mon, Nov 28, 2022 at 06:48:38PM -0800, Kevin J. McCarthy wrote:
> On Mon, Nov 28, 2022 at 07:45:00PM -0600, David Vernet wrote:
> > On Mon, Nov 28, 2022 at 04:14:10PM -0800, Matthew Sotoudeh via Mutt-dev
> > wrote:
> > > Per feedback from Kevin & David (thanks!), moved the timeout code into
> >
On Mon, Nov 28, 2022 at 07:45:00PM -0600, David Vernet wrote:
On Mon, Nov 28, 2022 at 04:14:10PM -0800, Matthew Sotoudeh via Mutt-dev wrote:
Per feedback from Kevin & David (thanks!), moved the timeout code into
socket_connect and updated the description to be more descriptive and
more closely m
On Mon, Nov 28, 2022 at 04:14:10PM -0800, Matthew Sotoudeh via Mutt-dev wrote:
> Per feedback from Kevin & David (thanks!), moved the timeout code into
> socket_connect and updated the description to be more descriptive and
> more closely match the existing connect_timeout.
I'm not sure how the mu
Per feedback from Kevin & David (thanks!), moved the timeout code into
socket_connect and updated the description to be more descriptive and
more closely match the existing connect_timeout.
There is some open question about where exactly in socket_connect to put
the timeout code. Currently I put i
