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

Re: [PATCH v4 1/1] archive-zip: refactor 'path too long' error message to use Q_()

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 22, 2026, 17:41 UTC
Message-ID
<xmqq1p9hhbue.fsf@gitster.g>
In-Reply-To
<57e076d3-cfea-475d-b68d-a9f36746db35@gmail.com>
Phillip Wood <phillip.wood123@gmail.com> writes:
Show 31 quoted lines
> Hi Keryle
>
> On 20/10/2026 19:39, kerylefondji7@gmail.com wrote:
>> 
>> diff --git a/archive-zip.c b/archive-zip.c
>> index 6f73ca6d58..5ab3ba786f 100644
>> --- a/archive-zip.c
>> +++ b/archive-zip.c
>> @@ -328,8 +328,10 @@ static int write_zip_entry(struct archiver_args *args,
>>   	}
>>   
>>   	if (pathlen > 0xffff) {
>> -		return error(_("path too long (%d chars, SHA1: %s): %s"),
>> -				(int)pathlen, oid_to_hex(oid), path);
>> +	 return error(Q_("path too long (%d char, SHA1: %s): %s",
>> +	  "path too long (%d chars, SHA1: %s): %s",
>> +	 pathlen),
>> +		(int)pathlen, oid_to_hex(oid), path);
>
> The indentation is still messed up. If you look at the deleted lines you can see that
> we've lost a level of indentation inside the "if" block and the function arguments no
> longer line up. It should look like
>
> 	if (pathlen > 0xffff) {
> 		return error(Q_("path too long (%d char, SHA1: %s): %s",
> 				"path too long (%d chars, SHA1: %s): %s",
> 				pathlen),
> 			     (int)pathlen, oid_to_hex(oid), path);
> 	}
>
> Thanks

Thanks. Just in case Keryle is reading the message in a terminal or webmail app with variable width fonts, the easiest way to see what is wrong in the posted patch is to visit

  https://lore.kernel.org/git/57e076d3-cfea-475d-b68d-a9f36746db35@gmail.com/

which should show the patch in fixed-width font and even uses real tab chars properly (so you can click-hold on the left end of a line and move your mouse right to highlight the indentation to tell the difference between a run of spaces and a tab).

Previous: Phillip WoodNext: kerylefondji7@gmail.com
Message 10 of 18 in “archive-zip: refactor 'path too long' error message to use Q_()”
  1. archive-zip: refactor 'path too long' error message to use Q_()kerylefondji7@gmail.com, Oct 19, 2026
  2. Phillip WoodOct 19, 2026
  3. Junio C HamanoOct 19, 2026
  4. 0/1 archive-zip: refactor 'path too long' error messagekerylefondji7@gmail.com, Oct 20, 2026
  5. 1/1 archive-zip: refactor 'path too long' error message to use Q_()kerylefondji7@gmail.com, Oct 20, 2026
  6. Phillip WoodOct 20, 2026
  7. 0/1 archive-zip: refactor 'path too long' error message to use Q_()kerylefondji7@gmail.com, Oct 20, 2026
  8. 1/1 archive-zip: refactor 'path too long' error message to use Q_()kerylefondji7@gmail.com, Oct 20, 2026
  9. Phillip WoodOct 22, 2026
  10. Junio C HamanoOct 22, 2026
  11. 0/1 archive-zip: refactor 'path too long' error message to use Q_()kerylefondji7@gmail.com, Oct 23, 2026
  12. 1/1 archive-zip: refactor 'path too long' error message to use Q_()kerylefondji7@gmail.com, Oct 23, 2026
  13. Phillip WoodOct 23, 2026
  14. 0/1 archive-zip: refactor 'path too long' error message to use Q_()kerylefondji7@gmail.com, Oct 23, 2026
  15. 1/1 archive-zip: refactor 'path too long' error message to use Q_()kerylefondji7@gmail.com, Oct 23, 2026
  16. kerylefondji7@gmail.comOct 26, 2026
  17. Junio C HamanoOct 26, 2026
  18. kerylefondji7@gmail.comOct 22, 2026

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.