From: Eric Anholt <eric@anholt.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Stefan Wahren <stefan.wahren@i2se.com>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: error when fetching the bcm2835 tree
Date: Tue, 04 Sep 2018 10:41:22 -0700 [thread overview]
Message-ID: <87wos1gny5.fsf@anholt.net> (raw)
In-Reply-To: <20180828074200.440fb5ca@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 662 bytes --]
Stephen Rothwell <sfr@canb.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?
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-09-04 17:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 21:42 linux-next: error when fetching the bcm2835 tree Stephen Rothwell
2018-09-04 17:41 ` Eric Anholt [this message]
2018-09-04 20:07 ` Stefan Wahren
2018-09-04 23:55 ` 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=87wos1gny5.fsf@anholt.net \
--to=eric@anholt.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=stefan.wahren@i2se.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox