git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Define a version of lstat(2) with posix semantics

From
Alex Riesen <raa.lkml@gmail.com>
Date
Mar 20, 2009, 08:30 UTC
Message-ID
<81b0412b0903200130s594ce3beyae21eb0b5cc8fe0@mail.gmail.com>
In-Reply-To
<alpine.DEB.1.00.0903200025170.10279@pacific.mpi-cbg.de>
2009/3/20 Johannes Schindelin <Johannes.Schindelin@gmx.de>:
Show 12 quoted lines
> 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).

Previous: Johannes SchindelinNext: Johannes Schindelin
Message 6 of 13 in “Define a version of lstat(2) with posix semantics”
  1. Define a version of lstat(2) with posix semanticsAlex Riesen, Mar 19, 2009
  2. Johannes SchindelinMar 19, 2009
  3. Alex RiesenMar 19, 2009
  4. git clone needs to know executability of template filesAlex Riesen, Mar 19, 2009
  5. Johannes SchindelinMar 19, 2009
  6. Alex RiesenMar 20, 2009
  7. Johannes SchindelinMar 20, 2009
  8. Alex RiesenMar 20, 2009
  9. Rogan DawesMar 20, 2009
  10. Alex RiesenMar 20, 2009
  11. Johannes SchindelinMar 20, 2009
  12. Alex RiesenMar 20, 2009
  13. Junio C HamanoMar 19, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.