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

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

From
PWPhillip Wood <phillip.wood123@gmail.com>
Date
Oct 23, 2026, 15:09 UTC
Message-ID
<8b75a831-f8b7-4e8d-9dbf-0f7fca5e7bc7@gmail.com>
In-Reply-To
<20261023120358.8061-2-kerylefondji7@gmail.com>
Hi Keryle
On 23/10/2026 13:03, kerylefondji7@gmail.com wrote:
Show 15 quoted lines
> > diff --git a/archive-zip.c b/archive-zip.c
> index 5ab3ba786f..160efd878f 100644
> --- a/archive-zip.c
> +++ b/archive-zip.c
> @@ -328,10 +328,10 @@ static int write_zip_entry(struct archiver_args *args,
>   	}
>   >   	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);
> +		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 looks good, but this does not apply to master. When you get feedback about a patch, you should send an amended patch that applies to master, not a fix that applies on top of the patch you previously sent. If a patch series contains more than one patch, you can use "git rebase -i" to prepare the new version. If there is a single patch like this series you can use "git commit --amend".
Thanks
Phillip
Previous: kerylefondji7@gmail.comNext: kerylefondji7@gmail.com
Message 13 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.