Subject: Re: linux-next: error while fetching the spi-nor tree
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
References: <20171213075845.5923cc80@canb.auug.org.au>
From: Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>
Message-ID: <12d92a91-bacc-38ae-9906-ac83ed32a0f6@wedev4u.fr>
Date: Tue, 12 Dec 2017 22:24:17 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <20171213075845.5923cc80@canb.auug.org.au>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 979
Lines: 32

Hi Stephen,

I've just added 2 commits about 8 hours ago, nothing special.
Could the issue be explained by an unlikely bad timing?

I don't see anything wrong when fetching the tree or when browsing the
web server:
http://git.infradead.org/l2-mtd.git/shortlog/refs/heads/spi-nor/next

Please, let me know whether it was a spurious error or if it still doesn't
work. Currently, I don't know what's going on.

Anyway, thanks for your report.

Best regards,

Cyrille

Le 12/12/2017 à 21:58, Stephen Rothwell a écrit :
> Hi Cyrille,
> 
> Fetching the spi-nor tree
> (git://git.infradead.org/l2-mtd.git#spi-nor/next) this morning, I get
> theses errors:
> 
> remote: error: Could not read 6e408e3aa1643624ea7da50ad5b27a226a16a654
> remote: fatal: bad tree object 6e408e3aa1643624ea7da50ad5b27a226a16a654
> remote: aborting due to possible repository corruption on the remote side.
> fatal: protocol error: bad pack header
> 
> I wil continue to use the previously fetched tree.
>