public inbox for
 help / color / mirror / Atom feed
From: Brian Inglis <>
Cc: Thomas Dickey <>,
	Yaakov Selkowitz <>
Subject: Re: Change Upstream Source URIs to HTTPS
Date: Tue, 12 Apr 2022 11:58:20 -0600	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 2022-04-12 11:48, Brian Inglis wrote:> I have tried using your web 
archives in the past and found that> access to your are consistently > unreliable, 
and to your are > sometimes 
unreliable, resulting in download failures when accessed from > my 
desktop or our Scallywag CIs from Appveyor or Github, so reverted to > 
using your FTP archives to which access is consistently reliable.> 
Perhaps you could check your web site download see if you 
can determine the cause of the issue and if there is anything you can do 
to mitigate the issue?
[Sorry for premature send ;^> ]
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

  reply	other threads:[~2022-04-12 17:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2022-04-11 22:13 ` Fwd: update urls for cygwinports Yaakov Selkowitz
2022-04-12 12:54   ` Jon Turney
2022-04-12 17:48   ` Change Upstream Source URIs to HTTPS Brian Inglis
2022-04-12 17:58     ` Brian Inglis [this message]
     [not found]     ` <>
     [not found]       ` <>
2022-04-12 21:57         ` Brian Inglis
     [not found]           ` <>
2022-04-13  2:44             ` Brian Inglis

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:

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

  git send-email \ \ \ \ \ \

* 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).