From: Phillip Wood <phillip.wood123@gmail.com>
To: kerylefondji7@gmail.com, git@vger.kernel.org
Cc: gitster@pobox.com
Subject: Re: [PATCH v3 1/1] archive-zip: refactor 'path too long' error message to use Q_()
Date: Tue, 20 Oct 2026 16:05:06 +0100 [thread overview]
Message-ID: <c578557c-c38e-48f3-ba61-fb2e0b139099@gmail.com> (raw)
In-Reply-To: <20261020102210.829-2-kerylefondji7@gmail.com>
Hi Keryle
On 20/10/2026 11:22, kerylefondji7@gmail.com wrote:
> From: Keryle Fondji <kerylefondji7@gmail.com>
>
> @@ -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 seems to have got messed up here, the level is wrong and
it seems to contain spaces as well - if I apply the patch I see
Applying: archive-zip: refactor 'path too long' error message to use Q_()
.git/rebase-apply/patch:17: indent with spaces.
pathlen),
warning: 1 line applied after fixing whitespace errors.
The code should be wrapped so that lines are not much longer than 80
characters and should be indented with tabs (possibly followed by a few
spaces so that the arguments are aligned).
Thanks
Phillip
> }
>
> if (S_ISDIR(mode) || S_ISGITLINK(mode)) {
prev parent reply other threads:[~2026-10-20 15:05 UTC|newest]
Thread overview: 6+ 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 ` [PATCH v3 0/1] archive-zip: refactor 'path too long' error message kerylefondji7
2026-10-20 10:22 ` [PATCH v3 1/1] archive-zip: refactor 'path too long' error message to use Q_() kerylefondji7
2026-10-20 15:05 ` Phillip Wood [this message]
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=c578557c-c38e-48f3-ba61-fb2e0b139099@gmail.com \
--to=phillip.wood123@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kerylefondji7@gmail.com \
--cc=phillip.wood@dunelm.org.uk \
/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