From: Eric Sunshine <sunshine@sunshineco.com>
To: Joel Holdsworth <jholdsworth@nvidia.com>
Cc: Git List <git@vger.kernel.org>, Luke Diamand <luke@diamand.org>,
Junio C Hamano <gitster@pobox.com>,
Tzadik Vanderhoof <tzadik.vanderhoof@gmail.com>,
Dorgon Chang <dorgonman@hotmail.com>,
Joachim Kuebart <joachim.kuebart@gmail.com>,
Daniel Levin <dendy.ua@gmail.com>,
Johannes Schindelin <johannes.schindelin@gmx.de>,
Ben Keene <seraphire@gmail.com>,
Andrew Oakley <andrew@adoakley.name>
Subject: Re: [PATCH 3/3] git-p4: don't print shell commands as python lists
Date: Thu, 6 Jan 2022 12:09:36 -0500 [thread overview]
Message-ID: <CAPig+cTeh=PKsvftWL_WPKBzqYkNr3+rEfqAgOsyksROBk8q1Q@mail.gmail.com> (raw)
In-Reply-To: <20220105161451.56378-4-jholdsworth@nvidia.com>
On Thu, Jan 6, 2022 at 7:54 AM Joel Holdsworth <jholdsworth@nvidia.com> wrote:
> Previously the git-p4 script would log commands as stringified
> representations of the command parameter, leading to output such as
> this:
>
> Reading pipe: ['git', 'config', '--bool', 'git-p4.useclientspec']
>
> Now that all commands list objects, this patch instead joins the
> elements of the list into a single string so the output now looks more
> readable:
s/commands list/commands are list/
> Reading pipe: git config --bool git-p4.useclientspec
>
> Signed-off-by: Joel Holdsworth <jholdsworth@nvidia.com>
prev parent reply other threads:[~2022-01-06 17:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 16:14 [PATCH 0/3] git-p4: Rationalise command construction Joel Holdsworth
2022-01-05 16:14 ` [PATCH 1/3] git-p4: don't select shell mode using the type of the command argument Joel Holdsworth
2022-01-06 17:02 ` Eric Sunshine
2022-01-05 16:14 ` [PATCH 2/3] git-p4: pass command arguments as lists instead of using shell Joel Holdsworth
2022-01-05 16:14 ` [PATCH 3/3] git-p4: don't print shell commands as python lists Joel Holdsworth
2022-01-06 17:09 ` Eric Sunshine [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='CAPig+cTeh=PKsvftWL_WPKBzqYkNr3+rEfqAgOsyksROBk8q1Q@mail.gmail.com' \
--to=sunshine@sunshineco.com \
--cc=andrew@adoakley.name \
--cc=dendy.ua@gmail.com \
--cc=dorgonman@hotmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jholdsworth@nvidia.com \
--cc=joachim.kuebart@gmail.com \
--cc=johannes.schindelin@gmx.de \
--cc=luke@diamand.org \
--cc=seraphire@gmail.com \
--cc=tzadik.vanderhoof@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;
as well as URLs for NNTP newsgroup(s).