From: Junio C Hamano <gitster@pobox.com>
To: Joel Holdsworth <jholdsworth@nvidia.com>
Cc: git@vger.kernel.org,
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>,
Luke Diamand <luke@diamand.org>, Ben Keene <seraphire@gmail.com>,
Andrew Oakley <andrew@adoakley.name>
Subject: Re: [PATCH v2 1/2] git-p4: remove "delete" verb
Date: Mon, 20 Dec 2021 11:38:30 -0800 [thread overview]
Message-ID: <xmqqh7b3vzgp.fsf@gitster.g> (raw)
In-Reply-To: <20211217140547.2115095-2-jholdsworth@nvidia.com> (Joel Holdsworth's message of "Fri, 17 Dec 2021 14:05:46 +0000")
Joel Holdsworth <jholdsworth@nvidia.com> writes:
> The git-p4 "delete" verb is described as "A tool to debug the output of
> p4 -G". However, the implementation provided is of no useful benefit to
> either users or developers.
The same comment as 2/2 applies here, too. This time, however, I
think it would be much easier to give a proper analysis of what it
is designed to do and what it does, to convince readers why it is
too trivial to be worth having the code (compared to the PATCH 2/2).
Also, this is not about the "delete" verb, but the "debug" verb, no?
> Signed-off-by: Joel Holdsworth <jholdsworth@nvidia.com>
> ---
> Adds Signed-off-by tag
>
> git-p4.py | 16 ----------------
> 1 file changed, 16 deletions(-)
>
> diff --git a/git-p4.py b/git-p4.py
> index 2b4500226a..b7ed8e41ff 100755
> --- a/git-p4.py
> +++ b/git-p4.py
> @@ -1532,21 +1532,6 @@ def loadUserMapFromCache(self):
> except IOError:
> self.getUserMapFromPerforceServer()
>
> -class P4Debug(Command):
> - def __init__(self):
> - Command.__init__(self)
> - self.options = []
> - self.description = "A tool to debug the output of p4 -G."
> - self.needsGit = False
> -
> - def run(self, args):
> - j = 0
> - for output in p4CmdList(args):
> - print('Element: %d' % j)
> - j += 1
> - print(output)
> - return True
> -
> class P4RollBack(Command):
> def __init__(self):
> Command.__init__(self)
> @@ -4363,7 +4348,6 @@ def printUsage(commands):
> print("")
>
> commands = {
> - "debug" : P4Debug,
> "submit" : P4Submit,
> "commit" : P4Submit,
> "sync" : P4Sync,
next prev parent reply other threads:[~2021-12-20 19:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 14:05 [PATCH v2 0/2] git-p4: remove "debug" and "rollback" verbs Joel Holdsworth
2021-12-17 14:05 ` [PATCH v2 1/2] git-p4: remove "delete" verb Joel Holdsworth
2021-12-20 19:38 ` Junio C Hamano [this message]
2021-12-21 10:32 ` Luke Diamand
2021-12-17 14:05 ` [PATCH v2 2/2] git-p4: remove "rollback" verb Joel Holdsworth
2021-12-20 19:32 ` Junio C Hamano
2021-12-20 21:19 ` [PATCH v2 0/2] git-p4: remove "debug" and "rollback" verbs Johannes Schindelin
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=xmqqh7b3vzgp.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=andrew@adoakley.name \
--cc=dendy.ua@gmail.com \
--cc=dorgonman@hotmail.com \
--cc=git@vger.kernel.org \
--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).