Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760033AbaJ1IaQ (ORCPT ); Tue, 28 Oct 2014 04:30:16 -0400 Received: from bastet.se.axis.com ([195.60.68.11]:38564 "EHLO bastet.se.axis.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752620AbaJ1IaK (ORCPT ); Tue, 28 Oct 2014 04:30:10 -0400 Date: Tue, 28 Oct 2014 09:30:03 +0100 From: Jesper Nilsson To: Stephen Rothwell Cc: Jesper Nilsson , "linux-next@vger.kernel.org" , "linux-kernel@vger.kernel.org" Subject: Re: linux-next: error fetching the cris tree Message-ID: <20141028083002.GK30087@axis.com> References: <20141028110857.06bfae62@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20141028110857.06bfae62@canb.auug.org.au> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/