public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesper Nilsson <jesper.nilsson@axis.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jesper Nilsson <jespern@axis.com>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: error fetching the cris tree
Date: Tue, 28 Oct 2014 09:30:03 +0100	[thread overview]
Message-ID: <20141028083002.GK30087@axis.com> (raw)
In-Reply-To: <20141028110857.06bfae62@canb.auug.org.au>

On Tue, Oct 28, 2014 at 01:08:57AM +0100, Stephen Rothwell wrote:
> Hi Jesper,

Hi Stephen!

> Fetching the cris tree (git://www.jni.nu/cris.git#for-next) this
> morning produced this error:
> 
> fatal: Couldn't find remote ref refs/heads/for-next

Ah sorry, my bad, I just changed the cris-mirror to copy from my
kernel.org tree, which had no for-next branch. Re-pushed now,
so it should be ok after the mirror has updated.

However, it might be better to switch over linux-next for cris
to use the for-next branch of this tree:

git://git.kernel.org/pub/scm/linux/kernel/git/jesper/cris.git

Should go a bit faster from there. The old mirror (repo.or.cz) will still
be there, but the tree at jni.nu will probably not come back.

> I will use the cris tree from yesterday.

Thanks,

/^JN - Jesper Nilsson
-- 
               Jesper Nilsson -- jesper.nilsson@axis.com

  reply	other threads:[~2014-10-28  8:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-28  0:08 linux-next: error fetching the cris tree Stephen Rothwell
2014-10-28  8:30 ` Jesper Nilsson [this message]
2014-10-28 12:27   ` 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=20141028083002.GK30087@axis.com \
    --to=jesper.nilsson@axis.com \
    --cc=jespern@axis.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