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

Re: [PATCH] CYGWIN: Use a TCP socket for pipe()

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 30, 2013, 22:56 UTC
Message-ID
<7vwqpbi4ws.fsf@alter.siamese.dyndns.org>
In-Reply-To
<51D08B58.8000103@web.de>
Torsten Bögershausen <tboegi@web.de> writes:
Show 6 quoted lines
> I testet "rj/cygwin-remove-cheating-lstat" with the "socket pipe" on top:
> no hanging.
>
> Then I run "rj/cygwin-remove-cheating-lstat" without "socket pipe",
> (or in other words git.git/pu):
> No hanging.
So an immediate conclusion is that we can forget about this patch?
> So at the moment I don't have any problems to report for cygwin, which is good.
>
> And it looks as if "rj/cygwin-remove-cheating-lstat" prevents the "hanging",
> so there is another +1 to keep it and move it into next.

Ramsay started a "mark places we call lstat() when we do not really need fully correct lstat" topic, and I think it may be a sane direction to go, as long as the helper function's semantic is clearly defined.

It would be worth seeing where it leads us, before ripping that "cheating and incomplete lstat out, I think.

Previous: Torsten BögershausenNext: Torsten Bögershausen
Message 5 of 6 in “CYGWIN: Use a TCP socket for pipe()”
  1. CYGWIN: Use a TCP socket for pipe()Torsten Bögershausen, Jun 27, 2013
  2. Junio C HamanoJun 27, 2013
  3. Mark LevedahlJun 28, 2013
  4. Torsten BögershausenJun 30, 2013
  5. Junio C HamanoJun 30, 2013
  6. Torsten BögershausenJul 2, 2013

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.