From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin source problem with git ?
Date: Tue, 24 May 2016 18:38:00 -0000 [thread overview]
Message-ID: <20160524143546.GE32753@calimero.vinschen.de> (raw)
In-Reply-To: <66fa4555-a404-f7b6-dc58-470b0616ac3f@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 782 bytes --]
On May 24 15:57, Marco Atzeri wrote:
> $ git clone git://sourceware.org/git/newlib-cygwin.git
> Cloning into 'newlib-cygwin'...
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
>
>
> cygwin-setup shows the same issue.
>
> cygwin-htdocs seems fine.
That also somtimes occurs when calling `git fetch' or something similiar.
It happens when sourceware is under heavy load apparently. You either
have to persist retrying, or you try dumb https as transport instead. It
mostly works even when the git service bucks.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-05-24 14:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 15:53 Marco Atzeri
2016-05-24 18:38 ` Corinna Vinschen [this message]
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=20160524143546.GE32753@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).