{"thread":{"id":"66670","subject":"[PATCH v7 0/1] archive-zip: refactor 'path too long' error message","startedAt":"2026-10-26T19:04:21Z","lastAt":"2026-10-27T19:33:37Z","messageCount":7,"participants":["kerylefondji7@gmail.com","Junio C Hamano"],"isPatch":true,"patchVersion":7,"patchTotal":1},"messages":[{"id":"556391","messageId":"20261026190423.1925-1-kerylefondji7@gmail.com","threadId":"66670","inReplyTo":"xmqotsm8qsdl.fsf@gitster.g","subject":"[PATCH v7 0/1] archive-zip: refactor 'path too long' error message","fromName":"","fromEmail":"kerylefondji7@gmail.com","sentAt":"2026-10-26T19:04:21Z","receivedAt":"2026-10-26T19:04:21Z","isPatch":true,"sender":{"key":"kerylefondji7@gmail.com","avatar":null},"body":"From: Keryle Fondji \n\nThis v7 addresses the feedback from Junio C Hamano and Phillip Wood regarding\ncommit structure, missing commit log message, and patch threading.\n\nIn previous attempts (like v5), the diff showed 4 deletions and 4 insertions\nbecause it was compared against prior iteration attempts. Since this v7 is\nflattened into a single clean commit applied directly on top of master, the\ndiff naturally shows 2 deletions (-) (removing the original master lines) and\n4 insertions (+) (adding the complete Q_() structure with correct tab/space\nalignments).\n\nRegarding the mistakes in previous iterations:\n- The commit message body was inadvertently omitted, which has now been fully\n restored.\n- An incorrect Message-ID was used for threading (replying to an older\n reference instead of the proper discussion thread), which is also corrected.\n\nSummary of changes in v7:\n- Rebased as a single clean commit directly on top of master.\n- Maintained the exact indentation approved in v5.\n- Restored the full commit log message and proper Signed-off-by signature.\n- Cleaned up unrelated modifications from the working directory.\n\nKeryle Fondji (1):\n archive-zip: refactor 'path too long' error message to use Q_()\n\n archive-zip.c | 6 ++++--\n 1 file changed, 4 insertions(+), 2 deletions(-)\n\n-- \n2.53.0\n\n\n"},{"id":"556392","messageId":"20261026190423.1925-2-kerylefondji7@gmail.com","threadId":"66670","inReplyTo":"20261026190423.1925-1-kerylefondji7@gmail.com","subject":"[PATCH v7 1/1] archive-zip: refactor 'path too long' error message to use Q_()","fromName":"","fromEmail":"kerylefondji7@gmail.com","sentAt":"2026-10-26T19:04:22Z","receivedAt":"2026-10-26T19:04:22Z","isPatch":true,"sender":{"key":"kerylefondji7@gmail.com","avatar":null},"body":"From: Keryle Fondji \n\nReplace _() with Q_() in the 'path too long' error message. Although\npathlen is always greater than 0xffff when this error is hit, Q_() is\nrequired to support correct translation for languages that require\ndifferent plural forms depending on the count.\n\nSigned-off-by: Keryle Fondji \n---\n archive-zip.c | 6 ++++--\n 1 file changed, 4 insertions(+), 2 deletions(-)\n\ndiff --git a/archive-zip.c b/archive-zip.c\nindex 6f73ca6d58..160efd878f 100644\n--- a/archive-zip.c\n+++ b/archive-zip.c\n@@ -328,8 +328,10 @@ static int write_zip_entry(struct archiver_args *args,\n \t}\n \n \tif (pathlen > 0xffff) {\n-\t\treturn error(_(\"path too long (%d chars, SHA1: %s): %s\"),\n-\t\t\t\t(int)pathlen, oid_to_hex(oid), path);\n+\t\treturn error(Q_(\"path too long (%d char, SHA1: %s): %s\",\n+\t\t\t\t\"path too long (%d chars, SHA1: %s): %s\",\n+\t\t\t\tpathlen),\n+\t\t\t (int)pathlen, oid_to_hex(oid), path);\n \t}\n \n \tif (S_ISDIR(mode) || S_ISGITLINK(mode)) {\n-- \n2.53.0\n\n\n"},{"id":"556396","messageId":"20261026192803.1985-1-kerylefondji7@gmail.com","threadId":"66670","inReplyTo":"xmqotsm8qsdl.fsf@gitster.g","subject":"[PATCH v7 0/1] archive-zip: refactor 'path too long' error message","fromName":"","fromEmail":"kerylefondji7@gmail.com","sentAt":"2026-10-26T19:28:02Z","receivedAt":"2026-10-26T19:28:02Z","isPatch":true,"sender":{"key":"kerylefondji7@gmail.com","avatar":null},"body":"From: Keryle Fondji \n\nThis v7 addresses the feedback from Junio C Hamano and Phillip Wood regarding\ncommit structure, missing commit log message, and patch threading.\n\nIn previous attempts (like v5), the diff showed 4 deletions and 4 insertions\nbecause it was compared against prior iteration attempts. Since this v7 is\nflattened into a single clean commit applied directly on top of master, the\ndiff naturally shows 2 deletions (-) (removing the original master lines) and\n4 insertions (+) (adding the complete Q_() structure with correct tab/space\nalignments).\n\nRegarding the mistakes in previous iterations:\n- The commit message body was inadvertently omitted, which has now been fully\n restored.\n- An incorrect Message-ID was used for threading (replying to an older\n reference instead of the proper discussion thread), which is also corrected.\n\nSummary of changes in v7:\n- Rebased as a single clean commit directly on top of master.\n- Maintained the exact indentation approved in v5.\n- Restored the full commit log message and proper Signed-off-by signature.\n- Cleaned up unrelated modifications from the working directory.\n\nKeryle Fondji (1):\n archive-zip: refactor 'path too long' error message to use Q_()\n\n archive-zip.c | 6 ++++--\n 1 file changed, 4 insertions(+), 2 deletions(-)\n\n-- \n2.53.0\n\n\n"},{"id":"556397","messageId":"20261026192803.1985-2-kerylefondji7@gmail.com","threadId":"66670","inReplyTo":"20261026192803.1985-1-kerylefondji7@gmail.com","subject":"[PATCH v7 1/1] archive-zip: refactor 'path too long' error message to use Q_()","fromName":"","fromEmail":"kerylefondji7@gmail.com","sentAt":"2026-10-26T19:28:03Z","receivedAt":"2026-10-26T19:28:03Z","isPatch":true,"sender":{"key":"kerylefondji7@gmail.com","avatar":null},"body":"From: Keryle Fondji \n\nReplace _() with Q_() in the 'path too long' error message. Although\npathlen is always greater than 0xffff when this error is hit, Q_() is\nrequired to support correct translation for languages that require\ndifferent plural forms depending on the count.\n\nSigned-off-by: Keryle Fondji \n---\n archive-zip.c | 6 ++++--\n 1 file changed, 4 insertions(+), 2 deletions(-)\n\ndiff --git a/archive-zip.c b/archive-zip.c\nindex 6f73ca6d58..160efd878f 100644\n--- a/archive-zip.c\n+++ b/archive-zip.c\n@@ -328,8 +328,10 @@ static int write_zip_entry(struct archiver_args *args,\n \t}\n \n \tif (pathlen > 0xffff) {\n-\t\treturn error(_(\"path too long (%d chars, SHA1: %s): %s\"),\n-\t\t\t\t(int)pathlen, oid_to_hex(oid), path);\n+\t\treturn error(Q_(\"path too long (%d char, SHA1: %s): %s\",\n+\t\t\t\t\"path too long (%d chars, SHA1: %s): %s\",\n+\t\t\t\tpathlen),\n+\t\t\t (int)pathlen, oid_to_hex(oid), path);\n \t}\n \n \tif (S_ISDIR(mode) || S_ISGITLINK(mode)) {\n-- \n2.53.0\n\n\n"},{"id":"556402","messageId":"xmqqpkwwp5hu.fsf@gitster.g","threadId":"66670","inReplyTo":"20261026190423.1925-2-kerylefondji7@gmail.com","subject":"Re: [PATCH v7 1/1] archive-zip: refactor 'path too long' error message to use Q_()","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-10-26T20:32:45Z","receivedAt":"2026-10-26T20:32:45Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"kerylefondji7@gmail.com writes:\n\nA few things.\n\n * Please do not send the same [v7] multiple times.\n\n * Please do not send your [v7] cover letter as a respopnse to a\n random other message; instead make it in resonse to previous\n rounds (either [v6] or [v1]).\n\nThese harm automation. Also\n\n * Patches [1/n]..[n/n] should be sent as a response to cover letter\n [0/n].\n\nThis [v7 1/1] correctly responds to [v7 0/1], but if gotten wrong,\nit would harm automation, too.\n\nIt also is more usual to send a single patch without cover letter.\n\n> From: Keryle Fondji \n>\n> Replace _() with Q_() in the 'path too long' error message. Although\n> pathlen is always greater than 0xffff when this error is hit, Q_() is\n> required to support correct translation for languages that require\n> different plural forms depending on the count.\n\nNicely described.\n\n> Signed-off-by: Keryle Fondji \n> ---\n> archive-zip.c | 6 ++++--\n> 1 file changed, 4 insertions(+), 2 deletions(-)\n\n> diff --git a/archive-zip.c b/archive-zip.c\n> index 6f73ca6d58..160efd878f 100644\n> --- a/archive-zip.c\n> +++ b/archive-zip.c\n> @@ -328,8 +328,10 @@ static int write_zip_entry(struct archiver_args *args,\n> \t}\n> \n> \tif (pathlen > 0xffff) {\n> -\t\treturn error(_(\"path too long (%d chars, SHA1: %s): %s\"),\n> -\t\t\t\t(int)pathlen, oid_to_hex(oid), path);\n> +\t\treturn error(Q_(\"path too long (%d char, SHA1: %s): %s\",\n> +\t\t\t\t\"path too long (%d chars, SHA1: %s): %s\",\n> +\t\t\t\tpathlen),\n> +\t\t\t (int)pathlen, oid_to_hex(oid), path);\n> \t}\n\nThis is outside the scope of this patch, but we may want to update\n\"SHA1\" with something like \"object name\", so that the error message\nworks even in SHA-256 repository.\n\n\n"},{"id":"556458","messageId":"20261027085042.7150-1-kerylefondji7@gmail.com","threadId":"66670","inReplyTo":"20261026192803.1985-2-kerylefondji7@gmail.com","subject":"Re: [PATCH v7 1/1] archive-zip: replace _() with Q_() in path too long error","fromName":"","fromEmail":"kerylefondji7@gmail.com","sentAt":"2026-10-27T08:50:42Z","receivedAt":"2026-10-27T08:50:42Z","isPatch":true,"sender":{"key":"kerylefondji7@gmail.com","avatar":null},"body":"Hi Junio,\n\nThank you for your feedback on v7.\n\nJust to be completely sure I understood correctly: regarding your note\nabout updating \"SHA1\" to \"object name\" being outside the scope of this\npatch, does this mean my current work on this patch is finished,\nor is there any additional change expected from me?\n\nThank you,\nKeryle\n\n"},{"id":"556566","messageId":"xmqq4ie7j5v2.fsf@gitster.g","threadId":"66670","inReplyTo":"20261027085042.7150-1-kerylefondji7@gmail.com","subject":"Re: [PATCH v7 1/1] archive-zip: replace _() with Q_() in path too long error","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-10-27T19:33:37Z","receivedAt":"2026-10-27T19:33:37Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"kerylefondji7@gmail.com writes:\n\n> Just to be completely sure I understood correctly: regarding your note\n> about updating \"SHA1\" to \"object name\" being outside the scope of this\n> patch, does this mean my current work on this patch is finished,\n> or is there any additional change expected from me?\n\nNot at this moment. The \"SHA1\" thing certainly is not something\nwe'd want to worry about.\n\nAs far as I am concerned, I think this topic is done. There might\nbe other issues raised by others later, though.\n\nThanks.\n\n\n"}]}