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

Re: [PATCH] git-p4: fix bug with encoding of p4 client name

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 8, 2022, 15:05 UTC
Message-ID
<xmqqmtdjwspm.fsf@gitster.g>
In-Reply-To
<CAPMMpohwP1U4pr-G=fDDu_AHTY-2mn8hn8zBf-pAsmm=w0mSzw@mail.gmail.com>
Tao Klerks <tao@klerks.biz> writes:
Show 24 quoted lines
>
>
> On Fri, Jul 8, 2022 at 10:01 AM Kilian Kilger via GitGitGadget
> <gitgitgadget@gmail.com> wrote:
>>
>> From: Kilian Kilger <kilian.kilger@sap.com>
>>
>> The Perforce client name can contain arbitrary characters
>> which do not decode to UTF-8. Use the fallback strategy
>> implemented in metadata_stream_to_writable_bytes() also
>> for the client name.
>>
>> Signed-off-by: Kilian Kilger <kkilger@gmail.com>
>> ---
>> ...
>>
>> @@ -871,6 +871,8 @@ def p4CmdList(cmd, stdin=None, stdin_mode='w+b', cb=None, skip_info=False,
>>                      continue
>>              if 'desc' in entry:
>>                  entry['desc'] = metadata_stream_to_writable_bytes(entry['desc'])
>> +            if 'client' in entry:
>> +                entry['client'] = metadata_stream_to_writable_bytes(entry['client'])
>>              if 'FullName' in entry:
>>                  entry['FullName'] = metadata_stream_to_writable_bytes(entry['FullName']

We had two repetitions and now we have three, which is a good time to see if it makes sense to reduce the temptation for future developers to add the fourth repetition in the next round, e.g.

	for e in ["client", "desc", "FullName"]:
		if e in entry:
			entry[e] = metadata_stream_to_writable_bytes(entry[e])
or something like that?
> This makes sense to me, and I don't see anything wrong with the "form"
> (and nor does GitGitGadget).

One thing that is a bit problematic is that in-body From does not match the sign-off. Kilian, which identity do you want to use in your contribution to this project?

> Not sure whether formal review sign-off is used on this list, I don't
> tend to see it, but do I see "Reviewed-by" on patches, so FWIW:
>
> Reviewed-by: Tao Klerks <tao@klerks.biz>
Thanks.
Previous: Tao KlerksNext: Kilian Kilger via GitGitGadget
Message 3 of 9 in “git-p4: fix bug with encoding of p4 client name”
  1. git-p4: fix bug with encoding of p4 client nameKilian Kilger via GitGitGadget, Jul 8, 2022
  2. Tao KlerksJul 8, 2022
  3. Junio C HamanoJul 8, 2022
  4. git-p4: fix bug with encoding of p4 client nameKilian Kilger via GitGitGadget, Jul 18, 2022
  5. Junio C HamanoJul 18, 2022
  6. 0/2 git-p4: Fix bug with encoding of P4 client nameKilian Kilger via GitGitGadget, Jul 21, 2022
  7. 1/2 git-p4: fix bug with encoding of p4 client nameKilian Kilger via GitGitGadget, Jul 21, 2022
  8. 2/2 git-p4: refactoring of p4CmdList()Kilian Kilger via GitGitGadget, Jul 21, 2022
  9. Junio C HamanoJul 21, 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.