* linux-next: unable to fetch the mvebu tree
@ 2019-06-02 22:23 Stephen Rothwell
2019-06-03 14:11 ` Gregory CLEMENT
0 siblings, 1 reply; 3+ messages in thread
From: Stephen Rothwell @ 2019-06-02 22:23 UTC (permalink / raw)
To: Jason Cooper, Andrew Lunn, Gregory Clement, ARM
Cc: Linux Next Mailing List, Linux Kernel Mailing List
[-- Attachment #1.1: Type: text/plain, Size: 240 bytes --]
Hi all,
Tyring to fetch the mvebu tree
(git://git.infradead.org/linux-mvebu.git#for-next) for the past several
days produces this error message:
fatal: Couldn't find remote ref refs/heads/for-next
--
Cheers,
Stephen Rothwell
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: linux-next: unable to fetch the mvebu tree
2019-06-02 22:23 linux-next: unable to fetch the mvebu tree Stephen Rothwell
@ 2019-06-03 14:11 ` Gregory CLEMENT
2019-06-03 14:20 ` Stephen Rothwell
0 siblings, 1 reply; 3+ messages in thread
From: Gregory CLEMENT @ 2019-06-03 14:11 UTC (permalink / raw)
To: Stephen Rothwell, Jason Cooper, Andrew Lunn, ARM
Cc: Linux Next Mailing List, Linux Kernel Mailing List
Hi Stephen,
> Hi all,
>
> Tyring to fetch the mvebu tree
> (git://git.infradead.org/linux-mvebu.git#for-next) for the past several
> days produces this error message:
>
> fatal: Couldn't find remote ref refs/heads/for-next
Sorry for this, the main reason was that I didn't create a for-next
branch for this new cycle.
I was waiting for 5.2-rc1 and then didn't take time to merge our current
branches in the for-next branch.
But now it should be available.
Gregory
>
> --
> Cheers,
> Stephen Rothwell
--
Gregory Clement, Bootlin
Embedded Linux and Kernel engineering
http://bootlin.com
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: linux-next: unable to fetch the mvebu tree
2019-06-03 14:11 ` Gregory CLEMENT
@ 2019-06-03 14:20 ` Stephen Rothwell
0 siblings, 0 replies; 3+ messages in thread
From: Stephen Rothwell @ 2019-06-03 14:20 UTC (permalink / raw)
To: Gregory CLEMENT
Cc: Jason Cooper, Andrew Lunn, ARM, Linux Next Mailing List,
Linux Kernel Mailing List
[-- Attachment #1: Type: text/plain, Size: 203 bytes --]
Hi Gregory,
On Mon, 03 Jun 2019 16:11:51 +0200 Gregory CLEMENT <gregory.clement@bootlin•com> wrote:
>
> But now it should be available.
Looks good now, thanks.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-06-03 14:20 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-06-02 22:23 linux-next: unable to fetch the mvebu tree Stephen Rothwell
2019-06-03 14:11 ` Gregory CLEMENT
2019-06-03 14:20 ` Stephen Rothwell
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox