git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Riesen <raa.lkml@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Git Mailing List <git@vger.kernel.org>,
	Johannes Sixt <j.sixt@viscovery.net>, Jeff King <peff@peff.net>,
	layer <layer@known.net>, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] Define a version of lstat(2) with posix semantics
Date: Fri, 20 Mar 2009 09:30:34 +0100	[thread overview]
Message-ID: <81b0412b0903200130s594ce3beyae21eb0b5cc8fe0@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0903200025170.10279@pacific.mpi-cbg.de>

2009/3/20 Johannes Schindelin <Johannes.Schindelin@gmx.de>:
> On Thu, 19 Mar 2009, Alex Riesen wrote:
>> Johannes Schindelin, Thu, Mar 19, 2009 11:57:01 +0100:
>>
>> > I'd rather just disable WIN32_STAT for Cygwin, because otherwise, we
>> > will keep running into issues.
>>
>> I'd rather not. The thing is just so unbelievably slow and being stuck
>> on it I'm just trying my damnedest to squeeze every last bit of
>> performance out of it.
>
> If you are serious about performance, you will not stay with Cygwin -- for
> the purposes of Git.

I'm staying with Cygwin port not _for_ Git, but _because_ of Cygwin. If it
were for me, I'd gladly let the Cygwin port die (frankly, any Windows port).
I just use Linux everywhere possible. Sometimes it's not...

> Do not get me wrong: Cygwin is a wonderful thing if your goal is to spare
> yourself a lot of trouble with that seriously challenged win32 API.

I beg to differ: Cygwin is a piece of crap and performs dangerously hideous
in what it tries to do.

> But if your goal is to get the most out of the Win32 API in terms of
> speed, you _will_ have to go with MinGW (at least, as long as you are
> unwilling to shell out big bucks in the vague direction of Redmond, and
> add some time tax to that).

My goal in this environment is to make it bearable. I think that both
Cygwin and MinGW ports are dead-on-arrival, because the underlying
platform is so stupidly and hopelessly broken, and no amount of no bucks
can help it.

> Now, we _do_ have msysGit, you _do_ have shown the capability to fix
> issues when they arise, so I do _not_ see any obstacle why you should not
> go msysGit, rather than staying with the pain of trying to stay
> POSIX-compatible, but not quite all the time.

I understand. It is not pure POSIX compatibility I seek. I just can't use MinGW
port, because I absolutely must use the cygwin environment (for "hysterical"
reasons) and they don't play well together (tried, yes. Conflicting libraries,
but you already know that).

I don't have the Windows sickness anywhere else but at my work, and
sadly it is a good place in all respects, even if absolute crazy in this regard.

So I'm sorry, if I ever made an impression that I'm motivated to do any
Windows-related development. I'm _absolutely_ not. I just happen to have that
itch of Perforce (may it burn in hell for thousand years), have a know how, and
have a little time to spare (hopefully no one of management sees that).

  reply	other threads:[~2009-03-20  8:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-19 10:27 [PATCH] Define a version of lstat(2) with posix semantics Alex Riesen
2009-03-19 10:57 ` Johannes Schindelin
2009-03-19 21:40   ` Alex Riesen
2009-03-19 21:43     ` [PATCH] git clone needs to know executability of template files Alex Riesen
2009-03-19 23:30     ` [PATCH] Define a version of lstat(2) with posix semantics Johannes Schindelin
2009-03-20  8:30       ` Alex Riesen [this message]
2009-03-20  9:17         ` Johannes Schindelin
2009-03-20 13:39           ` Alex Riesen
2009-03-20 13:49             ` Rogan Dawes
2009-03-20 14:17               ` Alex Riesen
2009-03-20 13:52             ` Johannes Schindelin
2009-03-20 14:20               ` Alex Riesen
2009-03-19 22:08   ` Junio C Hamano

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=81b0412b0903200130s594ce3beyae21eb0b5cc8fe0@mail.gmail.com \
    --to=raa.lkml@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=j.sixt@viscovery.net \
    --cc=layer@known.net \
    --cc=peff@peff.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).