All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Kastrup <dak@gnu.org>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: "Vicent Martí" <tanoku@gmail.com>, "Jeff King" <peff@peff.net>,
	"Git Mailing List" <git@vger.kernel.org>
Subject: Re: pack bitmap woes on Windows
Date: Wed, 12 Feb 2014 13:55:58 +0100	[thread overview]
Message-ID: <87mwhwa3s1.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <52FB2268.7080906@viscovery.net> (Johannes Sixt's message of "Wed, 12 Feb 2014 08:27:36 +0100")

Johannes Sixt <j.sixt@viscovery.net> writes:

> Running test suite of 'next' on Windows fails in t5310-pack-bitmaps with
> the following symptoms. I haven't followed the topic. Have there been
> patches floating that addressed the problem in one way or another?
>
> (gdb) run
> Starting program: D:\Src\mingw-git\t\trash directory.t5310-pack-bitmaps/..\..\git.exe rev-list --test-bitmap HEAD
> [New thread 3528.0x8d4]
> Bitmap v1 test (20 entries loaded)
> Found bitmap for 537ea4d3eb79c95f602873b1167c480006d2ac2d. 64 bits / 15873b36 checksum

Does reverting a201c20b41a2f0725977bcb89a2a66135d776ba2 help?

-- 
David Kastrup

  parent reply	other threads:[~2014-02-12 12:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-12  7:27 pack bitmap woes on Windows Johannes Sixt
2014-02-12 11:56 ` Erik Faye-Lund
2014-02-12 12:44   ` Johannes Sixt
2014-02-12 12:55 ` David Kastrup [this message]
2014-02-12 13:05   ` Johannes Sixt
2014-02-12 13:23     ` David Kastrup
2014-02-12 14:09       ` Duy Nguyen
2014-02-12 14:22         ` Erik Faye-Lund
2014-02-12 14:49           ` Erik Faye-Lund
2014-02-12 16:48             ` Jeff King
2014-02-13  8:07               ` Johannes Sixt

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=87mwhwa3s1.fsf@fencepost.gnu.org \
    --to=dak@gnu.org \
    --cc=git@vger.kernel.org \
    --cc=j.sixt@viscovery.net \
    --cc=peff@peff.net \
    --cc=tanoku@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.