From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gregory CLEMENT Subject: Re: linux-next: unable to fetch the mvebu tree Date: Mon, 03 Jun 2019 16:11:51 +0200 Message-ID: <87y32ikbbs.fsf@FE-laptop> References: <20190603082346.7bd1d7a4@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain Return-path: In-Reply-To: <20190603082346.7bd1d7a4@canb.auug.org.au> Sender: linux-kernel-owner@vger.kernel.org To: Stephen Rothwell , Jason Cooper , Andrew Lunn , ARM Cc: Linux Next Mailing List , Linux Kernel Mailing List List-Id: linux-next.vger.kernel.org Hi Stephen, > Hi all, > > Tyring to fetch the mvebu tree > (git://git.infradead.org/linux-mvebu.git#for-next) for the past several > days produces this error message: > > fatal: Couldn't find remote ref refs/heads/for-next Sorry for this, the main reason was that I didn't create a for-next branch for this new cycle. I was waiting for 5.2-rc1 and then didn't take time to merge our current branches in the for-next branch. But now it should be available. Gregory > > -- > Cheers, > Stephen Rothwell -- Gregory Clement, Bootlin Embedded Linux and Kernel engineering http://bootlin.com From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.0 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS,T_DKIMWL_WL_HIGH,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D8423C04AB5 for ; Mon, 3 Jun 2019 14:12:16 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id AB21C27AD2 for ; Mon, 3 Jun 2019 14:12:16 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="lv/GZmv4" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org AB21C27AD2 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=bootlin.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:Message-ID:Date:References :In-Reply-To:Subject:To:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=KVNhwWDnSqShnX4TpJXC8BbxdGkVlw32UoMNomRhRYA=; b=lv/GZmv4vi2KR1 0Kix5KP4v7S/DRXZchPT/VMcmlbY4q7V8IXGwGHj7EnEQrICOe/qaz8FRIUKKx76fHmx7qsu6KMEu OrLDDIzNYl/lpV40hSCnu3EQq61XX/3BcgTnFmHAM+X21AFdfdo3Q6YPiBvs+9IzY0PVxMKxKz6Q7 e0s8jxrcxWtRhAVAcIllt87cz03reVst5svCTNtQRDb8KxfBAWCAqSn11KgU6Sj/hiKU66QpAU9Mt iHpRMrJUMTf7q71R5wsTrC9iIlAZRCJhKL77iTdRWTN7d5+E2duNpS3sK8Qu9z7W8QQ8X0kJnCb/S nbaybt4WbamvonGbeyZw==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.90_1 #2 (Red Hat Linux)) id 1hXnh7-0006rJ-8N; Mon, 03 Jun 2019 14:12:13 +0000 Received: from relay4-d.mail.gandi.net ([217.70.183.196]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1hXnh3-0006qQ-9W for linux-arm-kernel@lists.infradead.org; Mon, 03 Jun 2019 14:12:11 +0000 X-Originating-IP: 92.137.69.152 Received: from localhost (alyon-656-1-672-152.w92-137.abo.wanadoo.fr [92.137.69.152]) (Authenticated sender: gregory.clement@bootlin.com) by relay4-d.mail.gandi.net (Postfix) with ESMTPSA id 0F1D1E0004; Mon, 3 Jun 2019 14:11:52 +0000 (UTC) From: Gregory CLEMENT To: Stephen Rothwell , Jason Cooper , Andrew Lunn , ARM Subject: Re: linux-next: unable to fetch the mvebu tree In-Reply-To: <20190603082346.7bd1d7a4@canb.auug.org.au> References: <20190603082346.7bd1d7a4@canb.auug.org.au> Date: Mon, 03 Jun 2019 16:11:51 +0200 Message-ID: <87y32ikbbs.fsf@FE-laptop> MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190603_071210_491810_96DBCAA7 X-CRM114-Status: UNSURE ( 8.53 ) X-CRM114-Notice: Please train this message. X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Linux Next Mailing List , Linux Kernel Mailing List Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hi Stephen, > Hi all, > > Tyring to fetch the mvebu tree > (git://git.infradead.org/linux-mvebu.git#for-next) for the past several > days produces this error message: > > fatal: Couldn't find remote ref refs/heads/for-next Sorry for this, the main reason was that I didn't create a for-next branch for this new cycle. I was waiting for 5.2-rc1 and then didn't take time to merge our current branches in the for-next branch. But now it should be available. Gregory > > -- > Cheers, > Stephen Rothwell -- Gregory Clement, Bootlin Embedded Linux and Kernel engineering http://bootlin.com _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel