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

Re: [PATCH v2 6/6] receive-pack: Send hook output over side band #2

From
Larry D'Anna <larry@elder-gods.org>
Date
Feb 9, 2010, 17:33 UTC
Message-ID
<20100209173307.GA1115@cthulhu>
In-Reply-To
<20100209172027.GC26964@spearce.org>
* Shawn O. Pearce (spearce@spearce.org) [100209 12:20]:
Show 7 quoted lines
> Larry D'Anna <larry@elder-gods.org> wrote:
> > 
> > This breaks t5401.  See <7v4olqlva7.fsf@alter.siamese.dyndns.org> in another thread.
> 
> No.  Your patch causes t5401 to break.  If you apply this series on
> top of maint, its fine.  If you merge this series into master, and
> correctly fix the Win32 merge conflict in run-command.c, its fine.

Well, the version of this commit that's in pu is defiantly failing t5401 on my machine. Just tested it again with a clean build. My series isn't an ancestor of it either. Did you notice the failure is intermittent? You have to run it a few times before it fails.

       --larry
Previous: Shawn O. PearceNext: Larry D'Anna
Message 13 of 14 in “receive-pack hooks over sideband”
  1. 0/6 receive-pack hooks over sidebandShawn O. Pearce, Feb 5, 2010
  2. 1/6 run-command: Allow stderr to be a caller supplied pipeShawn O. Pearce, Feb 5, 2010
  3. 2/6 run-command: support custom fd-set in asyncShawn O. Pearce, Feb 5, 2010
  4. 3/6 send-pack: demultiplex a sideband stream with status dataShawn O. Pearce, Feb 5, 2010
  5. 4/6 receive-pack: Refactor how capabilities are shown to the clientShawn O. Pearce, Feb 5, 2010
  6. 5/6 receive-pack: Wrap status reports inside side-band-64kShawn O. Pearce, Feb 5, 2010
  7. Junio C HamanoFeb 5, 2010
  8. Shawn O. PearceFeb 5, 2010
  9. Junio C HamanoFeb 5, 2010
  10. 6/6 receive-pack: Send hook output over side band #2Shawn O. Pearce, Feb 5, 2010
  11. Larry D'AnnaFeb 9, 2010
  12. Shawn O. PearceFeb 9, 2010
  13. Larry D'AnnaFeb 9, 2010
  14. Larry D'AnnaFeb 9, 2010

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.