From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: Juergen Stuber <juergen@jstuber.net>
Cc: git@vger.kernel.org, jnareb@gmail.com
Subject: Re: jgit performance update
Date: Mon, 4 Dec 2006 00:39:00 +0100 [thread overview]
Message-ID: <200612040039.00315.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <874psceh4z.fsf@freitag.home.jstuber.net>
söndag 03 december 2006 23:42 skrev Juergen Stuber:
> Hi Jakub,
>
> Jakub Narebski <jnareb@gmail.com> writes:
> > GitWiki tells us about egit/jgit repository at
> > http://www.spearce.org/projects/scm/egit.git
>
> I tried to access that with git 1.4.4.1 from Debian but
>
> % git clone http://www.spearce.org/projects/scm/egit.git
>
> hangs, the first time after "walk
> e339766abc2b919e7bb396cae22ddef065821381", the second time after "walk
> 9eec90ec5da239e063eaff6305d77294dc03396e" which is the "walk" line just
> before it.
Works fine here. (git 1.4.4.gf05d).
>
> There's also the following error shortly after the start:
>
> error: File bc01ab9e5fcd26918d7a334207183fa57ff1ce50
> (http://www.spearce.org/projects/scm/egit.git/objects/75/1c8f2e504c40d1c41e
>bbd87d8f8968529e9c30) corrupt
Unfortunately, messages about corrupt objects are "normal" with clone over
http. I'm not sure it has to be that way though. Run git-fsck-objects to make
sure there are no errors. The hangs aren't normal.
-- robin
next prev parent reply other threads:[~2006-12-03 23:36 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 [this message]
2006-12-03 23:58 ` Jakub Narebski
2006-12-04 0:46 ` Shawn Pearce
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=200612040039.00315.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=juergen@jstuber.net \
/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).