From: Nicolas Pitre <nico@cam.org>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Efficiency of initial clone from server
Date: Sun, 11 Feb 2007 20:38:09 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0702112022430.1757@xanadu.home> (raw)
In-Reply-To: <9e4733910702111525x176053d3y9fd6d809ac447c0a@mail.gmail.com>
On Sun, 11 Feb 2007, Jon Smirl wrote:
> On 2/11/07, Shawn O. Pearce <spearce@spearce.org> wrote:
> > Jon Smirl <jonsmirl@gmail.com> wrote:
> > > remote: Total 63, written 63 (delta 0), reused 63 (delta 0)
> > > 100% (63/63) done
> > > fatal: pack: not a valid SHA1
> > > New branch: 0953670fbcb75e26fb93340bddae934e85618f2e
> >
> > What version of git is this? That looks like we're assuming the word
> > pack was an object, but I'm not sure why we would do such a thing...
This "pack" comes from pack-index when providing the name of the pack.
It is either "pack" or "keep" and specifies the name of the .keep file
to remove in the later case.
This is caught by git-fetch.sh with some code identified with a comment
that reads: "# special line coming from index-pack with the pack name"
> jonsmirl@jonsmirl:/usr/local/bin$ git --version
> git version 1.5.0.rc2.g53551-dirty
You must have conflicting vintage of GIT installations on your machine
with missing support for the "pack" and "keep" stuff described above.
Nicolas
next prev parent reply other threads:[~2007-02-12 1:38 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-11 19:53 Efficiency of initial clone from server Jon Smirl
2007-02-11 22:53 ` Shawn O. Pearce
2007-02-11 23:25 ` Jon Smirl
2007-02-11 23:51 ` Jon Smirl
2007-02-12 1:38 ` Nicolas Pitre [this message]
2007-02-12 2:15 ` Jon Smirl
2007-02-12 3:55 ` Nicolas Pitre
2007-02-12 4:49 ` Shawn O. Pearce
2007-02-12 16:42 ` Nicolas Pitre
2007-02-12 4:16 ` Junio C Hamano
2007-02-12 4:29 ` Jon Smirl
2007-02-12 4:33 ` Junio C Hamano
2007-02-12 4:53 ` Jon Smirl
2007-02-12 5:01 ` Jon Smirl
2007-02-12 5:11 ` Shawn O. Pearce
2007-02-12 5:17 ` Jon Smirl
2007-02-12 15:20 ` Nicolas Pitre
2007-02-12 19:35 ` Theodore Tso
2007-02-12 20:53 ` Junio C Hamano
2007-02-12 21:33 ` Nicolas Pitre
2007-02-13 0:51 ` Jakub Narebski
2007-02-12 5:30 ` Junio C Hamano
2007-02-12 5:55 ` Jon Smirl
2007-02-12 6:08 ` Junio C Hamano
2007-02-12 15:24 ` Jon Smirl
2007-02-12 16:40 ` Jon Smirl
2007-02-12 17:04 ` Shawn O. Pearce
2007-02-12 11:45 ` Johannes Schindelin
2007-02-12 14:31 ` Jon Smirl
2007-02-12 17:06 ` Shawn O. Pearce
2007-02-13 15:03 ` Andreas Ericsson
2007-02-11 23:29 ` Jon Smirl
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=Pine.LNX.4.64.0702112022430.1757@xanadu.home \
--to=nico@cam.org \
--cc=git@vger.kernel.org \
--cc=jonsmirl@gmail.com \
--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).