* linux-next: unable to fetch the amlogic tree
@ 2016-11-15 22:18 Stephen Rothwell
2016-11-16 6:13 ` Kevin Hilman
0 siblings, 1 reply; 2+ messages in thread
From: Stephen Rothwell @ 2016-11-15 22:18 UTC (permalink / raw)
To: Kevin Hilman, Carlo Caione; +Cc: linux-next, linux-kernel
Hi all,
Fetching the amlogic tree
(git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-amlogic.git#for-next)
produces this error:
fatal: Couldn't find remote ref refs/heads/for-next
I will continue to use te previously fetched version of this tree.
--
Cheers,
Stephen Rothwell
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: linux-next: unable to fetch the amlogic tree
2016-11-15 22:18 linux-next: unable to fetch the amlogic tree Stephen Rothwell
@ 2016-11-16 6:13 ` Kevin Hilman
0 siblings, 0 replies; 2+ messages in thread
From: Kevin Hilman @ 2016-11-16 6:13 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: Carlo Caione, linux-next, lkml
HI Stephen,
On Tue, Nov 15, 2016 at 2:18 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> Fetching the amlogic tree
> (git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-amlogic.git#for-next)
> produces this error:
>
> fatal: Couldn't find remote ref refs/heads/for-next
Hmm, must've been bad timing. I was updating branches much earlier,
but maybe the your mirror didn't have it in time. Seems to be fully
mirrored now:
https://git.kernel.org/cgit/linux/kernel/git/khilman/linux-amlogic.git/log/?h=for-next
> I will continue to use te previously fetched version of this tree.
Should be fine for today.
Thanks,
Kevin
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2016-11-16 6:13 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-11-15 22:18 linux-next: unable to fetch the amlogic tree Stephen Rothwell
2016-11-16 6:13 ` Kevin Hilman
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 NNTP newsgroup(s).