[lkml]   [2017]   [Dec]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: linux-next: error while fetching the spi-nor tree
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:

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,


Le 12/12/2017 à 21:58, Stephen Rothwell a écrit :
> Hi Cyrille,
> Fetching the spi-nor tree
> (git:// 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.

 \ /
  Last update: 2017-12-12 22:24    [W:0.038 / U:3.144 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site