From: Junio C Hamano <gitster@pobox.com>
To: kerylefondji7@gmail.com
Cc: phillip.wood123@gmail.com, christian.couder@gmail.com,
siddharthasthana31@gmail.com, git@vger.kernel.org
Subject: Re: [PATCH v7 1/1] archive-zip: replace _() with Q_() in path too long error
Date: Tue, 27 Oct 2026 12:33:37 -0700 [thread overview]
Message-ID: <xmqq4ie7j5v2.fsf@gitster.g> (raw)
In-Reply-To: <20261027085042.7150-1-kerylefondji7@gmail.com> (kerylefondji7@gmail.com's message of "Tue, 27 Oct 2026 09:50:42 +0100")
kerylefondji7@gmail.com writes:
> Just to be completely sure I understood correctly: regarding your note
> about updating "SHA1" to "object name" being outside the scope of this
> patch, does this mean my current work on this patch is finished,
> or is there any additional change expected from me?
Not at this moment. The "SHA1" thing certainly is not something
we'd want to worry about.
As far as I am concerned, I think this topic is done. There might
be other issues raised by others later, though.
Thanks.
prev parent reply other threads:[~2026-10-27 19:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <xmqotsm8qsdl.fsf@gitster.g>
2026-10-26 19:04 ` [PATCH v7 0/1] archive-zip: refactor 'path too long' error message kerylefondji7
2026-10-26 19:04 ` [PATCH v7 1/1] archive-zip: refactor 'path too long' error message to use Q_() kerylefondji7
2026-10-26 20:32 ` Junio C Hamano
2026-10-26 19:28 ` [PATCH v7 0/1] archive-zip: refactor 'path too long' error message kerylefondji7
2026-10-26 19:28 ` [PATCH v7 1/1] archive-zip: refactor 'path too long' error message to use Q_() kerylefondji7
2026-10-27 8:50 ` [PATCH v7 1/1] archive-zip: replace _() with Q_() in path too long error kerylefondji7
2026-10-27 19:33 ` Junio C Hamano [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=xmqq4ie7j5v2.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=kerylefondji7@gmail.com \
--cc=phillip.wood123@gmail.com \
--cc=siddharthasthana31@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