From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Jason Cooper <jason@lakedaemon.net>, Andrew Lunn <andrew@lunn.ch>,
ARM <linux-arm-kernel@lists.infradead.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: unable to fetch the mvebu tree
Date: Mon, 03 Jun 2019 16:11:51 +0200 [thread overview]
Message-ID: <87y32ikbbs.fsf@FE-laptop> (raw)
In-Reply-To: <20190603082346.7bd1d7a4@canb.auug.org.au>
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
WARNING: multiple messages have this Message-ID (diff)
From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Jason Cooper <jason@lakedaemon.net>, Andrew Lunn <andrew@lunn.ch>,
ARM <linux-arm-kernel@lists.infradead.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: unable to fetch the mvebu tree
Date: Mon, 03 Jun 2019 16:11:51 +0200 [thread overview]
Message-ID: <87y32ikbbs.fsf@FE-laptop> (raw)
In-Reply-To: <20190603082346.7bd1d7a4@canb.auug.org.au>
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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-06-03 14:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-02 22:23 linux-next: unable to fetch the mvebu tree Stephen Rothwell
2019-06-02 22:23 ` Stephen Rothwell
2019-06-03 14:11 ` Gregory CLEMENT [this message]
2019-06-03 14:11 ` Gregory CLEMENT
2019-06-03 14:20 ` Stephen Rothwell
2019-06-03 14:20 ` 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=87y32ikbbs.fsf@FE-laptop \
--to=gregory.clement@bootlin.com \
--cc=andrew@lunn.ch \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--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.