git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Torsten Bögershausen" <tboegi@web.de>
To: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
Cc: "Johannes Sixt" <j6t@kdbg.org>,
	"Junio C Hamano" <gitster@pobox.com>,
	git@vger.kernel.org, "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>,
	"Stefan Zager" <szager@chromium.org>,
	"Torsten Bögershausen" <tboegi@web.de>
Subject: Re: What's cooking in git.git (Apr 2014, #01; Fri, 4)
Date: Tue, 08 Apr 2014 11:03:50 +0200	[thread overview]
Message-ID: <5343BB76.2000806@web.de> (raw)
In-Reply-To: <5342FFB4.3000200@ramsay1.demon.co.uk>

On 04/07/2014 09:42 PM, Ramsay Jones wrote:
> On 07/04/14 19:35, Johannes Sixt wrote:
>> Am 05.04.2014 11:19, schrieb Johannes Sixt:
>>> Am 04.04.2014 22:58, schrieb Junio C Hamano:
>>>> * sz/mingw-index-pack-threaded (2014-03-19) 1 commit
>>>>   - Enable index-pack threading in msysgit.
>>>>
>>>>   What is the status of this topic?  A failure report exists
>>>>   ($gmane/245170), and I am aware of Duy's $gmane/245034 but that was
>>>>   where the discussion stalled.  Is everybody waiting for everybody
>>>>   else to get the discussion unstuck?
>>> I still have to cross-check Duy's patch. I'll hopefully get to it in the
>>> next days and report back.
>> The test suite passes with Duy's patch ($gmane/245034), but t5302 fails
>> with this patch with a MinGW build. The patches touch the Cygwin
>> configuration, but I cannot test a Cygwin build.
> I haven't tested these on cygwin yet. However, only the old version of
> cygwin is affected (newer cygwin has a thread-safe pread) and, since I
> no longer have an old installation, I _can't_ test it anyway. :(
> (I updated cygwin earlier today and received a brand new cygwin dll
> with today's date!).
>
>> I have, however, lost track of what the objective of these patches is.
>> Is the threaded version significantly faster, and these patches are
>> worth it?
> Indeed. I haven't seen any numbers.
>
> ATB,
> Ramsay Jones
>
CYGWIN:
I managed to test under cygwin 1.7, commit 
03d9d2990b718ef6d859405af399f549c186b4d:
Test was OK.

MINWW: t5302 failed (same what Johannas reported)
  After reverting 9d66f2d97a97e08ae8d7c86 t5302 passed under MINGW

HTH
/Torsten

  reply	other threads:[~2014-04-08  9:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-04 20:58 What's cooking in git.git (Apr 2014, #01; Fri, 4) Junio C Hamano
2014-04-05  9:19 ` Johannes Sixt
2014-04-05 11:56   ` Torsten Bögershausen
2014-04-07 16:40   ` Junio C Hamano
2014-04-07 18:35   ` Johannes Sixt
2014-04-07 19:42     ` Ramsay Jones
2014-04-08  9:03       ` Torsten Bögershausen [this message]
2014-04-08  0:39     ` Duy Nguyen
2014-04-08 13:13       ` Johannes Sixt
2014-04-08 16:26         ` Junio C Hamano
2014-04-06 22:41 ` Philip Oakley

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5343BB76.2000806@web.de \
    --to=tboegi@web.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=j6t@kdbg.org \
    --cc=pclouds@gmail.com \
    --cc=ramsay@ramsay1.demon.co.uk \
    --cc=szager@chromium.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).