All of lore.kernel.org
 help / color / mirror / Atom feed
From: kerylefondji7@gmail.com
To: gitster@pobox.com
Cc: phillip.wood123@gmail.com, christian.couder@gmail.com,
	siddharthasthana31@gmail.com, git@vger.kernel.org,
	Keryle Fondji <kerylefondji7@gmail.com>
Subject: [PATCH v6 0/1] archive-zip: refactor 'path too long' error message to use Q_()
Date: Fri, 23 Oct 2026 22:38:12 +0100	[thread overview]
Message-ID: <20261023213813.3318-1-kerylefondji7@gmail.com> (raw)
In-Reply-To: <xmqq1p9hhbue.fsf@gitster.g>

From: Keryle Fondji <kerylefondji7@gmail.com>

This v6 addresses the feedback from Phillip Wood regarding commit
structure and patch applicability.

In previous attempts (like v5), the diff showed 4 deletions and 4
insertions because it was compared against prior iteration
attempts. Since this v6 is flattened into a single clean commit
applied directly on top of master, the diff naturally shows 2
deletions (-) (removing the original master lines) and 4
insertions (+) (adding the complete Q_() structure with correct
tab/space alignments).

Summary of changes in v6:
- Rebased as a single commit directly on top of master.
- Maintained the exact indentation approved in v5.
- Cleaned up unrelated modifications from the working directory.

Thanks again to Phillip Wood and Junio C Hamano for their guidance

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


  parent reply	other threads:[~2026-10-23 21:38 UTC|newest]

Thread overview: 16+ 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
2026-10-20 18:39     ` [PATCH v4 0/1] " kerylefondji7
2026-10-20 18:39       ` [PATCH v4 1/1] " kerylefondji7
2026-10-22 14:29         ` Phillip Wood
2026-10-22 17:41           ` Junio C Hamano
2026-10-23 12:03             ` [PATCH v5 0/1] " kerylefondji7
2026-10-23 12:03               ` [PATCH v5 1/1] " kerylefondji7
2026-10-23 15:09                 ` Phillip Wood
2026-10-23 21:38             ` kerylefondji7 [this message]
2026-10-23 21:38               ` [PATCH v6 " kerylefondji7
2026-10-22 10:28     ` [PATCH v4] archive-zip: refactor 'path too long' error 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=20261023213813.3318-1-kerylefondji7@gmail.com \
    --to=kerylefondji7@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.