linux-next: unable to fetch the mvebu tree

linux-next: unable to fetch the mvebu tree

[Stephen Rothwell]

[-- 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

Re: linux-next: unable to fetch the mvebu tree

[Gregory CLEMENT]

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

Re: linux-next: unable to fetch the mvebu tree

[Stephen Rothwell]

[-- 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 --]