| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20141028083002.GK30087@axis.com>
Date: Tue, 28 Oct 2014 09:30:03 +0100
From: Jesper Nilsson <jesper.nilsson@...s.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Jesper Nilsson <jespern@...s.com>,
"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: error fetching the cris tree
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@...s.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists