From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: error while fetching the spi-nor tree
Date: Wed, 13 Dec 2017 07:58:45 +1100 [thread overview]
Message-ID: <20171213075845.5923cc80@canb.auug.org.au> (raw)
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.
--
Cheers,
Stephen Rothwell
next reply other threads:[~2017-12-12 20:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 20:58 Stephen Rothwell [this message]
2017-12-12 21:24 ` linux-next: error while fetching the spi-nor tree Cyrille Pitchen
2017-12-12 22:35 ` Stephen Rothwell
2017-12-12 23:40 ` Stephen Rothwell
2017-12-12 22:53 ` Linus Torvalds
2017-12-12 23:48 ` Cyrille Pitchen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171213075845.5923cc80@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).