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

RE: [PATCH v2 RESEND 0/5] git-p4: fix RCS keyword processing encoding errors

From
Joel Holdsworth <jholdsworth@nvidia.com>
Date
Jan 4, 2022, 21:59 UTC
Message-ID
<BL0PR12MB4849438B1245FC1FCEE7ED0CC84A9@BL0PR12MB4849.namprd12.prod.outlook.com>
In-Reply-To
<xmqqh7ajb2bi.fsf@gitster.g>
> I do not see any difference between this version and what has been merged
> to 'next' at 650cb248 (2021-12-27).  Sent a wrong version?
Ah ok. I didn't realise that's how things are done around here. If the patches are accepted then this patch-set is unchanged and can be ignored.
Joel
Previous: Junio C HamanoNext: Junio C Hamano
Message 8 of 9 in “git-p4: fix RCS keyword processing encoding errors”
  1. 0/5 git-p4: fix RCS keyword processing encoding errorsJoel Holdsworth, Jan 4, 2022
  2. 1/5 git-p4: use with statements to close files after use in patchRCSKeywordsJoel Holdsworth, Jan 4, 2022
  3. 2/5 git-p4: pre-compile RCS keyword regexesJoel Holdsworth, Jan 4, 2022
  4. 3/5 git-p4: add raw option to read_pipelinesJoel Holdsworth, Jan 4, 2022
  5. 4/5 git-p4: open temporary patch file for write onlyJoel Holdsworth, Jan 4, 2022
  6. 5/5 git-p4: resolve RCS keywords in bytes not utf-8Joel Holdsworth, Jan 4, 2022
  7. Junio C HamanoJan 4, 2022
  8. Joel HoldsworthJan 4, 2022
  9. Junio C HamanoJan 4, 2022

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.