From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: linux-omap@vger.kernel.org
Subject: omapzoom tree broken?
Date: Tue, 9 Sep 2008 18:59:29 +0100 [thread overview]
Message-ID: <20080909175929.GK8894@flint.arm.linux.org.uk> (raw)
When trying to fetch the omapzoom tree, I get:
got a4ae90758b3c38012c875a62d0dd8a20a30e413b
walk a4ae90758b3c38012c875a62d0dd8a20a30e413b
Getting alternates list for http://git.omapzoom.org/repo/omapkernel
Getting pack list for http://git.omapzoom.org/repo/omapkernel
Getting index for pack 567cbb972dbfa42338e1269ca4a4a03ec2b1d35f
Resuming fetch of index for pack 567cbb972dbfa42338e1269ca4a4a03ec2b1d35f at byte 5890048
error: wrong index v1 file size in .git/objects/pack/pack-567cbb972dbfa42338e1269ca4a4a03ec2b1d35f.idx
Segmentation fault
Could we have it accessible via git the protocol please, rather than
http?
next reply other threads:[~2008-09-09 17:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 17:59 Russell King - ARM Linux [this message]
2008-09-09 18:37 ` omapzoom tree broken? Ashwin Bihari
2008-09-09 18:54 ` Russell King - ARM Linux
2008-09-10 19:08 ` Felipe Balbi
2008-09-11 10:20 ` Pandita, Vikram
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=20080909175929.GK8894@flint.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-omap@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