From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Nicolas Pitre" <nico@cam.org>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
"Martin Koegler" <mkoegler@auto.tuwien.ac.at>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: performance on repack
Date: Sat, 1 Sep 2007 17:54:31 -0400 [thread overview]
Message-ID: <9e4733910709011454w630c53ecj67d7980838b729c@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.0.999.0708300033540.16727@xanadu.home>
On 8/30/07, Nicolas Pitre <nico@cam.org> wrote:
> On Thu, 30 Aug 2007, Nicolas Pitre wrote:
>
> > Well, here is a quick implementation of this idea for those who would
> > like to give it a try.
> [...]
Appears to be broken for a push.
jonsmirl@terra:~/mpc5200b$ git push dreamhost
updating 'refs/remotes/linus/master' using 'refs/heads/master'
from d1caeb02b17c6bc215a9a40a98a1beb92dcbd310
to 40ffbfad6bb79a99cc7627bdaca0ee22dec526f6
Generating pack...
Counting objects: 1
Done counting 3255 objects.
Result has 1997 objects.
Deltifying 398 objects...
Deltifying 398 objects...
Deltifying 398 objects...
Deltifying 398 objects...
Deltifying 398 objects...
Deltifying 398 objects...
Deltifying 398 objects...
Deltifying 398 objects...
Deltifying 398 objects...
Deltifying 398 objects...
Deltifying 398 objects...
Deltifying 398 objects...
Deltifying 398 objects...
Deltifying 398 objects...
Deltifying 398 objects...
Deltifying 398 objects...
0% (2/398) donee
1% (4/398) donee
11% (47/398) done
3% (12/398) done
2% (8/398) donee
12% (49/398) done
17% (69/398) done
1% (4/398) donee
25% (100/398) done
19% (77/398) donee
23% (94/398) done
21% (84/398) done
25% (100/398) done
2% (10/398) done
1% (6/398) done
error: pack-objects died with strange error
unpack eof before pack header was fully read
ng refs/remotes/linus/master n/a (unpacker error)
error: failed to push to 'ssh://jonsmirl1@git.digispeaker.com/~/mpc5200b.git'
jonsmirl@terra:~/mpc5200b$
--
Jon Smirl
jonsmirl@gmail.com
prev parent reply other threads:[~2007-09-01 21:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-11 21:12 performance on repack Jon Smirl
2007-08-11 22:09 ` David Kastrup
2007-08-11 22:34 ` Linus Torvalds
2007-08-11 23:21 ` Jon Smirl
2007-08-12 10:33 ` Martin Koegler
2007-08-12 13:49 ` Jon Smirl
2007-08-14 3:12 ` Shawn O. Pearce
2007-08-14 4:10 ` Jon Smirl
2007-08-14 5:13 ` Shawn O. Pearce
2007-08-14 5:57 ` Jon Smirl
2007-08-14 14:52 ` Nicolas Pitre
2007-08-14 21:41 ` Nicolas Pitre
2007-08-15 1:20 ` Jon Smirl
2007-08-15 1:59 ` Nicolas Pitre
2007-08-15 5:32 ` Shawn O. Pearce
2007-08-15 15:08 ` Jon Smirl
2007-08-15 17:11 ` Martin Koegler
2007-08-15 18:38 ` Jon Smirl
2007-08-15 19:00 ` Nicolas Pitre
2007-08-15 19:42 ` Jon Smirl
2007-08-16 8:10 ` David Kastrup
2007-08-16 15:34 ` Nicolas Pitre
2007-08-16 16:13 ` Jon Smirl
2007-08-16 16:21 ` Nicolas Pitre
2007-08-15 21:05 ` Nicolas Pitre
2007-08-15 20:49 ` Nicolas Pitre
2007-08-30 4:27 ` Nicolas Pitre
2007-08-30 4:36 ` Nicolas Pitre
2007-08-30 16:17 ` Jon Smirl
2007-09-01 21:54 ` Jon Smirl [this message]
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=9e4733910709011454w630c53ecj67d7980838b729c@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=git@vger.kernel.org \
--cc=mkoegler@auto.tuwien.ac.at \
--cc=nico@cam.org \
--cc=spearce@spearce.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).