From: Shawn Pearce <spearce@spearce.org>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: jgit performance update
Date: Sun, 3 Dec 2006 19:46:10 -0500 [thread overview]
Message-ID: <20061204004610.GA16706@spearce.org> (raw)
In-Reply-To: <ekvoan$lst$1@sea.gmane.org>
Jakub Narebski <jnareb@gmail.com> wrote:
> I got:
> $ git clone http://www.spearce.org/projects/scm/egit.git
> [...]
> got 73ed47b2bb1fa5978f7368775979e5c85d354c5a
> error: File 2332eacf114debb7a27d138811197f06eb262551
> (http://www.spearce.org/projects/scm/egit.git/objects/75/1c8f2e504c40d1c41ebbd87d8f8968529e9c30) corrupt
> Getting pack list for http://www.spearce.org/projects/scm/egit.git/
> got afefbe09bacc08adb75fb46200a973001c6b02de
> [...]
> walk c1f287cb19b9910af19756cf29c08b1fda75da8c
> Some loose object were found to be corrupt, but they might be just
> a false '404 Not Found' error message sent with incorrect HTTP
> status code. Suggest running git fsck-objects.
> got eab86de8ac23e2e77878835007724146fdd83796
> $ git fsck-objects --unreachable --full --strict ;# returns no errors
Right. My web server doesn't send back 404 messages when an object
isn't found (but is packed). Thus the error...
I've setup a project on repo.or.cz:
http://repo.or.cz/w/egit.git
--
next prev parent reply other threads:[~2006-12-04 0:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-03 4:59 jgit performance update Shawn Pearce
2006-12-03 13:55 ` Robin Rosenberg
2006-12-03 14:19 ` Jakub Narebski
2006-12-03 15:53 ` Robin Rosenberg
2006-12-03 23:06 ` Shawn Pearce
2006-12-03 22:59 ` Shawn Pearce
2006-12-03 17:45 ` Linus Torvalds
2006-12-03 17:56 ` Jakub Narebski
2006-12-03 22:42 ` Juergen Stuber
2006-12-03 23:39 ` Robin Rosenberg
2006-12-03 23:58 ` Jakub Narebski
2006-12-04 0:46 ` Shawn Pearce [this message]
2006-12-04 20:35 ` Juergen Stuber
2006-12-03 22:47 ` Shawn Pearce
2006-12-03 21:55 ` sf
2006-12-03 22:16 ` Shawn Pearce
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=20061204004610.GA16706@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
/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).