From: Pierre Habouzit <madcoder@debian.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "Björn Steinbrink" <B.Steinbrink@gmx.de>,
spearce@spearce.org, "Git ML" <git@vger.kernel.org>,
"Junio C Hamano" <gitster@pobox.com>
Subject: Re: regression in 92392b4
Date: Wed, 23 Jul 2008 13:50:26 +0200 [thread overview]
Message-ID: <20080723115026.GH15243@artemis.madism.org> (raw)
In-Reply-To: <alpine.DEB.1.00.0807231235150.8986@racer>
[-- Attachment #1: Type: text/plain, Size: 1438 bytes --]
On Wed, Jul 23, 2008 at 11:37:00AM +0000, Johannes Schindelin wrote:
> Hi,
>
> On Wed, 23 Jul 2008, Pierre Habouzit wrote:
>
> > On Wed, Jul 23, 2008 at 10:49:04AM +0000, Johannes Schindelin wrote:
> >
> > > On Wed, 23 Jul 2008, Björn Steinbrink wrote:
> > > Funny. That does not reproduce the bug here at all.
> > >
> > > But then, it is unsurprising, since both Pierre and me did something
> > > similar yesterday, fetching _just_ the pre-fetch refs into a freshly
> > > initted Git repository, and then fetching from kernel.org.
> > >
> > > Tested on x86_64.
> >
> > I can reproduce on x86_64 here.
>
> Well, I cannot. However, I get some pread issue on i686. To be nice to
> kernel.org, I downloaded the pack in question:
>
> http://pacific.mpi-cbg.de/git/thin-pack.pack
>
> You should be able to reproduce the behavior by piping this into
>
> git-index-pack --stdin -v --fix-thin --keep=fetch-pack --pack_header=2,263
I can reproduce. Funily enough, I just happened to see that I have
core.deltabasecachelimit = 0 in my git.git repository... which I
probably used meaning -1 but oh well. The bottom line is that the
pruning algorithm likely removes a pointer we still have a pointer to
somewhere...
--
·O· Pierre Habouzit
··O madcoder@debian.org
OOO http://www.madism.org
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-07-23 11:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 23:17 regression in 92392b4 Pierre Habouzit
2008-07-22 23:34 ` Johannes Schindelin
2008-07-23 0:41 ` Shawn O. Pearce
2008-07-23 0:58 ` Johannes Schindelin
2008-07-23 1:09 ` Pierre Habouzit
2008-07-23 1:20 ` Johannes Schindelin
2008-07-22 23:37 ` Pierre Habouzit
2008-07-23 10:14 ` Björn Steinbrink
2008-07-23 10:22 ` Pierre Habouzit
2008-07-23 10:38 ` Pierre Habouzit
2008-07-23 10:49 ` Johannes Schindelin
2008-07-23 10:56 ` Björn Steinbrink
2008-07-23 11:19 ` Pierre Habouzit
2008-07-23 11:37 ` Johannes Schindelin
2008-07-23 11:50 ` Pierre Habouzit [this message]
2008-07-23 12:00 ` Björn Steinbrink
2008-07-23 12:11 ` [PATCH] index-pack: never prune base_cache Pierre Habouzit
2008-07-23 12:52 ` Björn Steinbrink
2008-07-23 13:09 ` Johannes Schindelin
2008-07-23 13:20 ` Pierre Habouzit
2008-07-23 13:46 ` Johannes Schindelin
2008-07-23 13:44 ` Björn Steinbrink
2008-07-23 14:41 ` Johannes Schindelin
2008-07-23 15:30 ` Pierre Habouzit
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=20080723115026.GH15243@artemis.madism.org \
--to=madcoder@debian.org \
--cc=B.Steinbrink@gmx.de \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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