From: Mark Salter <msalter@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: error when fetching the c6x tree
Date: Wed, 20 Apr 2016 10:33:57 -0400 [thread overview]
Message-ID: <1461162837.3897.4.camel@redhat.com> (raw)
In-Reply-To: <20160420073632.626a8b3b@canb.auug.org.au>
On Wed, 2016-04-20 at 07:36 +1000, Stephen Rothwell wrote:
> Hi Mark,
>
> Attempting to fetch the c6x tree
> (git://linux-c6x.org/git/projects/linux-c6x-upstreaming.git#for-linux-next)
> produced this error:
>
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
>
Thanks Stephen. It looks like there was some transient network issue
on the server end. It seems to be working now.
next prev parent reply other threads:[~2016-04-20 14:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 21:36 linux-next: error when fetching the c6x tree Stephen Rothwell
2016-04-20 14:33 ` Mark Salter [this message]
2016-04-21 0:01 ` Stephen Rothwell
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=1461162837.3897.4.camel@redhat.com \
--to=msalter@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.