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
Junio C Hamano <gitster@pobox.com>
Date
Jan 4, 2022, 21:47 UTC
Message-ID
<xmqqh7ajb2bi.fsf@gitster.g>
In-Reply-To
<20220104124913.2894-1-jholdsworth@nvidia.com>
Joel Holdsworth <jholdsworth@nvidia.com> writes:
> This patch-set fixes a family of issues with git-p4's handling of
> incoming text data that contains RCS keywords, when those files contain
> bytes which are invalid UTF-8 codes.

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?

In any case, if there is an update, since the original series is in 'next', please send in incremental changes on top of them.

Thanks.
Previous: Joel HoldsworthNext: Joel Holdsworth
Message 7 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.