[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1892655944.623.1536091635278@email.1und1.de>
Date: Tue, 4 Sep 2018 22:07:15 +0200 (CEST)
From: Stefan Wahren <stefan.wahren@...e.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
Eric Anholt <eric@...olt.net>
Cc: Linux-Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: error when fetching the bcm2835 tree
Hi,
> Eric Anholt <eric@...olt.net> hat am 4. September 2018 um 19:41 geschrieben:
>
>
> Stephen Rothwell <sfr@...b.auug.org.au> writes:
>
> > [ Unknown signature status ]
> > Hi Eric,
> >
> > Fetching the bcm2835 tree (git://github.com/anholt/linux.git#for-next)
> > produces this error:
> >
> > fatal: Couldn't find remote ref refs/heads/for-next
>
> I'd passed responsibility for the git tree off to Stefan while I'm
> mostly-unavailable due to new baby. Maybe Stefan had deleted the branch
> for a bit?
sorry for that. I deleted the branch and i manually setup the new one later.
I hope, everything is fine now?
>
> Stefan -- the for-next branch is what linux-next pulls in, and I was
> regenerating it whenever I pushed -next branches. You can find one set
> of scripts for helping generate a for-next branch at
> git://git.kernel.org/pub/scm/linux/kernel/git/tegra/maint-scripts.git
Cool
Stefan
Powered by blists - more mailing lists