From: Junio C Hamano <gitster@pobox.com>
To: "Phillip Wood via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Eric Sunshine <sunshine@sunshineco.com>,
Phillip Wood <phillip.wood@dunelm.org.uk>
Subject: Re: [PATCH] worktree: add -z option for list subcommand
Date: Fri, 25 Feb 2022 09:59:41 -0800 [thread overview]
Message-ID: <xmqqh78mesj6.fsf@gitster.g> (raw)
In-Reply-To: <pull.1164.git.1645801727732.gitgitgadget@gmail.com> (Phillip Wood via GitGitGadget's message of "Fri, 25 Feb 2022 15:08:47 +0000")
"Phillip Wood via GitGitGadget" <gitgitgadget@gmail.com> writes:
> +-z::
> + When `--porcelain` is specified with `list` terminate each line with a
> + NUL rather than a newline. This makes it possible to parse the output
> + when a worktree path contains a newline character.
This makes it sound as if it were impossible. As the changes this
patch makes to the documentation and the code indicate, we were
already doing quote_c_style(), so it is not quite correct to say so.
Perhaps "makes it easier" is more accurate?
Unless the original wasn't using quote_c_style() correctly and
wasn't quoting its output, that is?
> @@ -411,7 +417,8 @@ working tree itself.
>
> Porcelain Format
> ~~~~~~~~~~~~~~~~
> -The porcelain format has a line per attribute. Attributes are listed with a
> +The porcelain format has a line per attribute. If `-z` is given then the lines
> +are terminated with NUL rather than a newline. Attributes are listed with a
> label and value separated by a single space. Boolean attributes (like `bare`
> and `detached`) are listed as a label only, and are present only
> if the value is true. Some attributes (like `locked`) can be listed as a label
> @@ -449,7 +456,7 @@ prunable gitdir file points to non-existent location
>
> ------------
>
> -If the lock reason contains "unusual" characters such as newline, they
> +Unless `-z` is used any "unusual" characters in the lock reason such as newlines
> are escaped and the entire reason is quoted as explained for the
OK. That is sensible.
> reason = worktree_lock_reason(wt);
> if (reason && *reason) {
> struct strbuf sb = STRBUF_INIT;
> - quote_c_style(reason, &sb, NULL, 0);
> - printf("locked %s\n", sb.buf);
> + if (line_terminator) {
> + quote_c_style(reason, &sb, NULL, 0);
> + reason = sb.buf;
> + }
> + printf("locked %s%c", reason, line_terminator);
OK. I suspect write_name_quoted() may be a better fit that does not
require us to have our own strbuf, but this should be OK.
> strbuf_release(&sb);
> } else if (reason)
> - printf("locked\n");
> + printf("locked%c", line_terminator);
It is a shame that we need a special code path for an empty string
given as the reason, only for the single SP after "locked", but we
have to live with it, I guess.
> reason = worktree_prune_reason(wt, expire);
> if (reason)
> - printf("prunable %s\n", reason);
> + printf("prunable %s%c", reason, line_terminator);
>
> - printf("\n");
> + fputc(line_terminator, stdout);
> }
All code changes looked sensible.
> + else if (!line_terminator && !porcelain)
> + die(_("'-z' requires '--porcelain'"));
> else {
> struct worktree **worktrees = get_worktrees();
> int path_maxlen = 0, abbrev = DEFAULT_ABBREV, i;
> @@ -708,7 +716,8 @@ static int list(int ac, const char **av, const char *prefix)
>
> for (i = 0; worktrees[i]; i++) {
> if (porcelain)
> - show_worktree_porcelain(worktrees[i]);
> + show_worktree_porcelain(worktrees[i],
> + line_terminator);
> else
> show_worktree(worktrees[i], path_maxlen, abbrev);
> }
next prev parent reply other threads:[~2022-02-25 17:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 15:08 [PATCH] worktree: add -z option for list subcommand Phillip Wood via GitGitGadget
2022-02-25 17:59 ` Junio C Hamano [this message]
2022-02-28 8:35 ` Eric Sunshine
2022-02-28 16:10 ` Phillip Wood
2022-02-28 17:16 ` Junio C Hamano
2022-02-28 16:00 ` Phillip Wood
2022-02-28 8:16 ` Eric Sunshine
2022-02-28 11:08 ` Phillip Wood
2022-02-28 9:47 ` Jean-Noël Avila
2022-02-28 10:57 ` Phillip Wood
2022-03-31 16:21 ` [PATCH v2] " Phillip Wood via GitGitGadget
2022-03-31 20:37 ` Junio C Hamano
2022-04-04 15:47 ` Phillip Wood
2023-05-11 4:11 ` Eric Sunshine
-- strict thread matches above, loose matches on Subject: below --
2021-01-05 10:29 [PATCH 5/7] worktree: `list` escape lock reason in --porcelain Phillip Wood
2021-01-05 11:02 ` [PATCH] worktree: add -z option for list subcommand Phillip Wood
2021-01-07 3:34 ` Eric Sunshine
2021-01-08 10:33 ` Phillip Wood
2021-01-10 7:27 ` 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=xmqqh78mesj6.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=phillip.wood@dunelm.org.uk \
--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).