From: kerylefondji7@gmail.com
To: git@vger.kernel.org
Cc: phillip.wood123@gmail.com, gitster@pobox.com,
Keryle Fondji <kerylefondji7@gmail.com>
Subject: [PATCH v3 0/1] archive-zip: refactor 'path too long' error message
Date: Tue, 20 Oct 2026 11:22:09 +0100 [thread overview]
Message-ID: <20261020102210.829-1-kerylefondji7@gmail.com> (raw)
In-Reply-To: <xmqqmrs92y4c.fsf@gitster.g>
From: Keryle Fondji <kerylefondji7@gmail.com>
This v3 addresses the review feedback by wrapping the overly long line
in archive-zip.c, while keeping the proper use of Q_() for plural forms.
Keryle Fondji (1):
archive-zip: refactor 'path too long' error message to use Q_()
archive-zip.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
--
2.53.0
next prev parent reply other threads:[~2026-10-20 10:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 8:44 [PATCH] archive-zip: refactor 'path too long' error message to use Q_() kerylefondji7
2026-10-19 13:58 ` Phillip Wood
2026-10-19 21:12 ` Junio C Hamano
2026-10-20 10:22 ` kerylefondji7 [this message]
2026-10-20 10:22 ` [PATCH v3 1/1] " kerylefondji7
2026-10-20 15:05 ` Phillip Wood
2026-10-20 18:39 ` [PATCH v4 0/1] " kerylefondji7
2026-10-20 18:39 ` [PATCH v4 1/1] " kerylefondji7
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261020102210.829-1-kerylefondji7@gmail.com \
--to=kerylefondji7@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=phillip.wood123@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox