From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Boris Brezillon <boris.brezillon@collabora.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: error while fetching the i3c-fixes tree
Date: Sun, 3 Jan 2021 15:23:43 +0100 [thread overview]
Message-ID: <20210103142343.GC382945@piout.net> (raw)
In-Reply-To: <20210103151855.5d25ee80@collabora.com>
On 03/01/2021 15:18:55+0100, Boris Brezillon wrote:
> +Alexandre, the new I3C maintainer. You should probably flag him as the
> person to contact if you have problem with the I3C tree in the future.
>
> Hi Stephen,
>
> On Sun, 3 Jan 2021 22:32:17 +1100
> Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> > Hi all,
> >
> > Fetching the i3c-fixes tree
> > (git://git.kernel.org/pub/scm/linux/kernel/git/i3c/linux.git#master)
> > produces this error:
> >
> > fatal: couldn't find remote ref refs/heads/master
> >
> > Should I maybe use the i3c/fixes branch instead?
>
> Oops, I thought you were using that branch already. I guess I never
> noticed because I didn't use the fixes branch much and kept the master
> one around.
>
Yes, please use the i3c/fixes branch. I did indeed remove the master
branch as this was not used anyway.
--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-01-03 14:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-03 11:32 linux-next: error while fetching the i3c-fixes tree Stephen Rothwell
2021-01-03 14:18 ` Boris Brezillon
2021-01-03 14:23 ` Alexandre Belloni [this message]
2021-01-03 21: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=20210103142343.GC382945@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=boris.brezillon@collabora.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).