From: "Shawn O. Pearce" <spearce@spearce.org>
To: Robin Rosenberg <robin.rosenberg@dewire.com>
Cc: git@vger.kernel.org
Subject: Re: [JGIT PATCH 4/5] Add "jgit clone" to support cloning off URLs that are JGit specific
Date: Tue, 30 Dec 2008 23:35:05 -0800 [thread overview]
Message-ID: <20081231073505.GA22551@spearce.org> (raw)
In-Reply-To: <200812310812.15305.robin.rosenberg@dewire.com>
Robin Rosenberg <robin.rosenberg@dewire.com> wrote:
> Would it be hard to get the progress look better?
This happens because we are scanning the progress channel wrong in
some cases. Its random; most of the time we can get it right, but
every once in a while we get out of sync and get these short names.
This is a general problem with the progress client side code, not
the new server side code I've introduced. We also see it going
against a standard C git daemon. I haven't been able to figure
out a way to smooth out the messages.
FWIW, git-gui also gets this sort of progress corruption sometimes
when it does a clone. So I've reproduced the same parsing bug in
two different languages and two different implementations... ;-)
> EGIT.contrib/jgit clone git://repo.or.cz/libgit2.git LIBGIT2
> Initialized empty Git repository in /home/me/SW/LIBGIT2/.git
> Counting objects: 547
> Compressing objects: 100% (192/192)
> ts: 100% (192/192)
> Compressing objects: 100% (192/192)
> ng objects: 100% (192/192)
> Compressing objects: 100% (192/192)
> bjects: 100% (192/192)
> Compressing objects: 100% (192/192)
> pressing objects: 100% (192/192)
> ts: 100% (192/192)
> Compressing objects: 100% (192/192)
> Receiving objects: 100% (547/547)
> jects: 100% (192/192)
> Compressing objects: 100% (192/192)
> ressing objects: 100% (192/192)
> s: 100% (192/192)
> Compressing objects: 100% (192/192)
> ssing objects: 100% (192/192)
> ts: 100% (192/192)
> Compressing objects: 100% (192/192)
> objects: 100% (192/192)
> Compressing objects: 100% (192/192)
> essing objects: 100% (192/192)
> cts: 100% (192/192)
> Compressing objects: 100% (192/192)
> g objects: 100% (192/192)
> Compressing objects: 100% (192/192)
> ressing objects: 100% (192/192)
> Resolving deltas: 100% (358/358)
> From git://repo.or.cz/libgit2.git
> * [new branch] master -> origin/master
--
Shawn.
next prev parent reply other threads:[~2008-12-31 7:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-23 18:03 [JGIT PATCH 0/5] Add jgit init, clone, receive-pack; transport fixes Shawn O. Pearce
2008-12-23 18:03 ` [JGIT PATCH 1/5] Add "jgit receive-pack" and permit commands to start not in a repository Shawn O. Pearce
2008-12-23 18:03 ` [JGIT PATCH 2/5] Add "jgit init" command to create a new repository Shawn O. Pearce
2008-12-23 18:03 ` [JGIT PATCH 3/5] Modify "jgit daemon" so it can run outside of a repository Shawn O. Pearce
2008-12-23 18:03 ` [JGIT PATCH 4/5] Add "jgit clone" to support cloning off URLs that are JGit specific Shawn O. Pearce
2008-12-23 18:03 ` [JGIT PATCH 5/5] Fix "fetch pulled too many objects" when auto-following tags Shawn O. Pearce
2008-12-31 7:12 ` [JGIT PATCH 4/5] Add "jgit clone" to support cloning off URLs that are JGit specific Robin Rosenberg
2008-12-31 7:35 ` Shawn O. Pearce [this message]
2008-12-31 19:04 ` [JGIT PATCH] Improve the sideband progress scaper to be more accurate Shawn O. Pearce
2009-01-03 22:12 ` Robin Rosenberg
2009-01-06 19:23 ` Nicolas Pitre
2009-01-06 19:27 ` Shawn O. Pearce
2009-01-06 20:55 ` Nicolas Pitre
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=20081231073505.GA22551@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=robin.rosenberg@dewire.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).