From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: failure fetching the sunxi tree
Date: Thu, 5 Jan 2017 16:15:23 +0100 [thread overview]
Message-ID: <20170105151523.vec6dnldfbkce2mk@lukather> (raw)
In-Reply-To: <20170104093124.24147e05@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 862 bytes --]
Hi Stephen,
On Wed, Jan 04, 2017 at 09:31:24AM +1100, Stephen Rothwell wrote:
> Hi Maxime,
>
> On Wed, 21 Dec 2016 09:24:13 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > Trying to fetch the sunxi tree
> > (git://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git#sunxi/for-next),
> > produces this error:
> >
> > fatal: Couldn't find remote ref refs/heads/sunxi/for-next
>
> I am still getting this error.
Sorry, I went in holidays and removed that branch to avoid any
conflicts during the merge window... I didn't know it was an issue to
you and assumed that you would just ignore it, sorry for that, it
won't happen again.
Anyway, I just pushed a new one, so everything should be back to
normal.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2017-01-05 15:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-20 22:24 linux-next: failure fetching the sunxi tree Stephen Rothwell
2017-01-03 22:31 ` Stephen Rothwell
2017-01-05 15:15 ` Maxime Ripard [this message]
2017-01-05 22:50 ` 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=20170105151523.vec6dnldfbkce2mk@lukather \
--to=maxime.ripard@free-electrons.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 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.