From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Grant Likely <grant.likely@secretlab•ca>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: error trying to fetch the devicetree tree
Date: Fri, 26 Sep 2014 11:57:34 +1000 [thread overview]
Message-ID: <20140926115734.15aef23e@canb.auug.org.au> (raw)
In-Reply-To: <20140925144432.1794fdbe@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 548 bytes --]
Hi Grant,
On Thu, 25 Sep 2014 14:44:32 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> Fetching the devicetree tree
> (git://git.secretlab.ca/git/linux-2.6#devicetree/next) failes like this:
>
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
I changed to using git://git.secretlab.ca/git/linux (since that is what
you asked Linus to pull) and that seems to work.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-09-26 1:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 4:44 linux-next: error trying to fetch the devicetree tree Stephen Rothwell
2014-09-26 1:57 ` Stephen Rothwell [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=20140926115734.15aef23e@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=grant.likely@secretlab$(echo .)ca \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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