From: Nicolas Pitre <nico@cam.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: heads-up: git-index-pack in "next" is broken
Date: Tue, 17 Oct 2006 11:39:20 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0610171134130.1971@xanadu.home> (raw)
In-Reply-To: <7vy7rfsfqa.fsf@assigned-by-dhcp.cox.net>
On Mon, 16 Oct 2006, Junio C Hamano wrote:
> I'm still a bit under the weather and do not have enough
> concentration to dig into the problem tonight, but I noticed
> that something in "next", most likely the delta-base-offset
> patchset, broke git-index-pack:
>
> $ X=ec0c3491753e115e1775256f6b7bd1bce4dea7cd
> $ wget http://www.kernel.org/pub/scm/git/git.git/objects/pack/pack-$X.pack
> $ ~/git-master/bin/git-index-pack pack-$X.pack
> ec0c3491753e115e1775256f6b7bd1bce4dea7cd
> $ git-index-pack pack-$X.pack
> fatal: packfile 'pack-ec0c3491753e115e1775256f6b7bd1bce4dea7cd.pack' has unresolved deltas
Using the tip of the "next" branch (git version 1.4.2.4.gf9fe) I just
cannot reproduce this problem at all. I always get a good index and
ec0c3491753e115e1775256f6b7bd1bce4dea7cd back.
Nicolas
next prev parent reply other threads:[~2006-10-17 15:39 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 4:55 heads-up: git-index-pack in "next" is broken Junio C Hamano
2006-10-17 15:39 ` Nicolas Pitre [this message]
2006-10-17 16:07 ` Junio C Hamano
2006-10-17 17:00 ` Nicolas Pitre
2006-10-17 18:11 ` Junio C Hamano
2006-10-17 18:47 ` Nicolas Pitre
2006-10-17 19:36 ` Sergey Vlasov
2006-10-17 20:10 ` Junio C Hamano
2006-10-17 20:25 ` Nicolas Pitre
2006-10-17 20:23 ` Nicolas Pitre
2006-10-17 20:51 ` Linus Torvalds
2006-10-17 21:21 ` Nicolas Pitre
2006-10-17 21:46 ` Linus Torvalds
2006-10-18 0:20 ` Nicolas Pitre
2006-10-18 0:57 ` Linus Torvalds
2006-10-18 2:08 ` Nicolas Pitre
2006-10-18 3:12 ` Linus Torvalds
2006-10-18 6:09 ` Davide Libenzi
2006-10-18 14:56 ` Linus Torvalds
2006-10-18 16:17 ` Davide Libenzi
2006-10-18 16:52 ` Linus Torvalds
2006-10-18 21:21 ` Davide Libenzi
2006-10-18 21:48 ` Linus Torvalds
2006-10-18 22:34 ` Davide Libenzi
2006-10-18 1:30 ` Junio C Hamano
2006-10-18 2:23 ` Nicolas Pitre
2006-10-18 4:16 ` Junio C Hamano
2006-10-18 5:07 ` Junio C Hamano
2006-10-18 10:00 ` Johannes Schindelin
2006-10-18 13:13 ` Nicolas Pitre
2006-10-18 13:02 ` Nicolas Pitre
2006-10-17 21:54 ` Junio C Hamano
2006-10-18 1:38 ` 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=Pine.LNX.4.64.0610171134130.1971@xanadu.home \
--to=nico@cam.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).