All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Sixt <J.Sixt@eudaptics.com>
To: git@vger.kernel.org
Subject: Re: MinGW port usable
Date: Tue, 30 Jan 2007 09:45:46 +0100	[thread overview]
Message-ID: <45BF05BA.4B356B37@eudaptics.com> (raw)
In-Reply-To: Pine.LNX.4.64.0701291438580.3611@woody.linux-foundation.org

Linus Torvalds wrote:
> Can you elaborate about any performance differences, especially with
> cygwin? Does this make git perform reasonably on Windows, or are the
> performance problems as bad as with cygwin?

Performance is horrid, although better than I initially expected. I
don't (want to) have cygwin installed to compare it (that's why I did
the MinGW port in the first place ;) Maybe others can comment on this?

The test suite takes ~15min to complete on my box, which is an oooold
800MHz with a slow HD. (And it's still Win2K, if that matters.)

Quite frankly, the "performance boost" that I expect from this port is
that it allows me the workflow that I want, instead of constantly
banging my head against the walls of CVS/SVN/you-name-it.

> gitk really shouldn't use either. It should probably use
> 
>         git-show-ref -h -d
> 
> instead, which has the same output format (modulo a space vs tab issue),
> and is entirely local, with no silly unnecessary remote connext.

Thanks, this works (I tested Junio's version). The problem with
ls-remote was that it is a shell script, and for some reason it dumps
its output into a cmd.exe that opens and closes right away instead of to
the pipe.

-- Hannes

  parent reply	other threads:[~2007-01-30  8:44 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-29 22:20 MinGW port usable Johannes Sixt
2007-01-29 22:35 ` Shawn O. Pearce
2007-01-29 23:11   ` Christian MICHON
2007-01-29 23:24     ` Shawn O. Pearce
2007-01-29 23:48       ` Christian MICHON
2007-01-30  7:59       ` Christian MICHON
2007-01-30  8:07         ` Christian MICHON
2007-01-30 10:16           ` Johannes Schindelin
2007-01-30 15:27             ` Shawn O. Pearce
2007-01-30 16:31           ` Johannes Sixt
2007-01-30  8:47   ` Johannes Sixt
2007-01-29 22:46 ` Linus Torvalds
2007-01-29 23:08   ` Christian MICHON
2007-01-30 10:08     ` Johannes Schindelin
2007-01-30 10:14       ` Christian MICHON
2007-01-30  8:45   ` Johannes Sixt [this message]
2007-01-30 14:35   ` Johannes Schindelin
2007-01-30 15:18     ` Shawn O. Pearce
2007-01-30 15:38       ` Johannes Schindelin
2007-01-30 15:56         ` Shawn O. Pearce
2007-01-30 16:12           ` Johannes Schindelin
2007-01-30 16:28             ` Shawn O. Pearce
2007-01-30 16:49               ` Johannes Schindelin
2007-01-30  0:50 ` Daniel Barkalow
2007-01-30  8:23   ` Johannes Sixt
2007-01-30  8:41     ` Andreas Ericsson
2007-01-30 10:07     ` Johannes Schindelin
2007-01-30 17:09     ` Daniel Barkalow
2007-01-30 17:36       ` Johannes Schindelin
2007-01-30 18:09         ` Daniel Barkalow
2007-01-30 20:20           ` Johannes Sixt
2007-01-30  5:53 ` Junio C Hamano
2007-02-01  6:35 ` H. Peter Anvin
2007-02-01 10:34   ` Johannes Sixt
2007-02-01 21:05     ` H. Peter Anvin
2007-02-02  8:28       ` H. Peter Anvin
2007-02-02  8:49         ` Davide Libenzi
2007-02-02  8:55         ` Johannes Sixt
2007-02-02  8:55         ` H. Peter Anvin

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=45BF05BA.4B356B37@eudaptics.com \
    --to=j.sixt@eudaptics.com \
    --cc=git@vger.kernel.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 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.