Re: [PATCH v4 1/1] range-diff: treat notes like `log`

From: Junio C Hamano <gitster@pobox.com>
Date: Sep 19, 2023, 19:43 UTC
Message-ID: <xmqqfs3aeyo4.fsf@gitster.g>
In-Reply-To: <9f9610fa-f1cc-404a-9496-d8b77ca05d5b@app.fastmail.com>

"Kristoffer Haugsbakk" <code@khaugsbakk.name> writes:

Show 7 quoted lines

> The original CI failed.[1] Then I rebased on `master` (d4a83d07b8c (The
> tenth batch, 2023-09-18)) which also failed.[2] Problem in t5559.
>
> So: fair warning. :)
>
> [1] https://github.com/LemmingAvalanche/git/actions/runs/6238806624
> [2] https://github.com/LemmingAvalanche/git/actions/runs/6239585493

I think you can ignore these macOS ones that spew

    == Info: [HTTP/2] [1] ...

in the log. The adjustments necessary for the redaction code to deal with these new messages from cURL are known and are cooking.

$ 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.