From: Junio C Hamano <gitster@pobox.com>
To: Phillip Wood <phillip.wood123@gmail.com>
Cc: git@vger.kernel.org, Eric Sunshine <sunshine@sunshineco.com>
Subject: Re: [PATCH 0/2] worktree list: fix column alignment
Date: Tue, 18 Nov 2025 09:03:30 -0800 [thread overview]
Message-ID: <xmqqzf8je0il.fsf@gitster.g> (raw)
In-Reply-To: <cover.1763482051.git.phillip.wood@dunelm.org.uk> (Phillip Wood's message of "Tue, 18 Nov 2025 16:07:31 +0000")
Phillip Wood <phillip.wood123@gmail.com> writes:
> From: Phillip Wood <phillip.wood@dunelm.org.uk>
>
> If a worktree path contains a multibyte character we end up with
> excess padding between the columns in the output of "git worktree
> list". This series fixes that and quotes the path to avoid control
> characters messing up the output as well.
Great. Thanks.
>
> Base-Commit: fd372d9b1a69a01a676398882bbe3840bf51fe72
> Published-As: https://github.com/phillipwood/git/releases/tag/pw%2Fworktree-list-spacing%2Fv1
> View-Changes-At: https://github.com/phillipwood/git/compare/fd372d9b1...b42d0f668
> Fetch-It-Via: git fetch https://github.com/phillipwood/git pw/worktree-list-spacing/v1
>
>
> Phillip Wood (2):
> worktree list: fix column spacing
> worktree list: quote paths
>
> builtin/worktree.c | 41 ++++++++++++++++++++++++++++------------
> t/t2402-worktree-list.sh | 37 +++++++++++++++++++++++-------------
> 2 files changed, 53 insertions(+), 25 deletions(-)
next prev parent reply other threads:[~2025-11-18 17:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 16:07 [PATCH 0/2] worktree list: fix column alignment Phillip Wood
2025-11-18 16:07 ` [PATCH 1/2] worktree list: fix column spacing Phillip Wood
2025-11-19 6:55 ` Eric Sunshine
2025-11-18 16:07 ` [PATCH 2/2] worktree list: quote paths Phillip Wood
2025-11-19 7:09 ` Eric Sunshine
2025-11-21 16:20 ` Phillip Wood
2025-11-18 17:03 ` Junio C Hamano [this message]
2025-11-19 6:50 ` [PATCH 0/2] worktree list: fix column alignment Eric Sunshine
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=xmqqzf8je0il.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=phillip.wood123@gmail.com \
--cc=sunshine@sunshineco.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;
as well as URLs for NNTP newsgroup(s).