On 7/11/22 8:32 AM, Rebecca Cran wrote: > On Mon, Jul 11, 2022, at 7:54 AM, Jens Axboe wrote: >> On 7/10/22 8:55 PM, Rebecca Cran wrote: >>> Change git clone commands to specify https instead of git or http. >>> GitHub has removed support for the git protocol >>> (https://github.blog/changelog/2022-03-15-removed-unencrypted-git-protocol-and-certain-ssh-keys/) >>> and http accesses will normally redirect to https. >>> >>> Update links to use https where possible: all the sites with updated links >>> automatically redirect http accesses to https. >>> >>> Signed-off-by: Rebecca Cran <rebecca@xxxxxxxxx> >>> --- >>> README.rst | 27 ++++++-------------- >>> 1 file changed, 8 insertions(+), 19 deletions(-) >>> >>> diff --git a/README.rst b/README.rst >>> index 527f33ab..ce5c0707 100644 >>> --- a/README.rst >>> +++ b/README.rst >>> @@ -27,31 +27,20 @@ Source >>> >>> Fio resides in a git repo, the canonical place is: >>> >>> - git://git.kernel.dk/fio.git >>> - >>> -When inside a corporate firewall, git:// URL sometimes does not work. >>> -If git:// does not work, use the http protocol instead: >>> - >>> - http://git.kernel.dk/fio.git >>> + https://git.kernel.dk/fio.git >> >> I don't think you checked that one... I've fixed it up, looks like the >> cgit redirect doesn't always work reliably. > > I did check it: cloning worked, but accessing it in a web browser > didn?t work, and since accessing git:// in a web browser also doesn?t > work I decided to update it. https://git.kernel.dk/cgit/fio/ should work for both cloning and in a browser, which is why I made the update. -- Jens Axboe