From: David Aguilar <davvid@gmail.com>
To: Denton Liu <liu.denton@gmail.com>,
Johannes Schindelin <johannes.schindelin@gmx.de>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: [BUG] was: Re: [PATCH] Remove --no-gui option from difftool usage string
Date: Sun, 5 Feb 2017 12:17:51 -0800 [thread overview]
Message-ID: <20170205201751.z4rfmy5xxaqg472l@gmail.com> (raw)
In-Reply-To: <20170204025617.GA9221@arch-attack.localdomain>
On Fri, Feb 03, 2017 at 06:56:17PM -0800, Denton Liu wrote:
> The --no-gui option not documented in the manpage, nor is it actually
> used in the source code. This change removes it from the usage help
> that's printed.
>
> Signed-off-by: Denton Liu <liu.denton@gmail.com>
> ---
> git-difftool.perl | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
[Dscho, I found a bug, see below]
I forgot to mention that the scripted difftool has been
rewritten in C and will be going away soon.
builtin/difftool.c is already in "next".
New patches against difftool should target the builtin.
Regarding removing it from the usage string, IMO that can be
considered a good change if the rationale were instead that
we never expect users to ever type "--no-gui" in practice.
Wasting the short usage string screen space with a useless to
99.99% users option is bad for usability. From that perspective
we shouldn't mention it there, so reframing the commit message
towards that argument would make for a better motivation.
Removing the mention from the usage string and adding it to the
manpage would be the a good change from that perspective as well.
BTW, in "next", it seems that the builtin difftool crashes when
doing "git difftool -h", so we should probably add a test
for that too...
From the tip of next:
$ git difftool -h
fatal: BUG: setup_git_env called without repository
--
David
next prev parent reply other threads:[~2017-02-05 20:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-04 2:56 [PATCH] Remove --no-gui option from difftool usage string Denton Liu
2017-02-04 5:58 ` Jacob Keller
2017-02-04 6:23 ` Denton Liu
2017-02-05 10:22 ` David Aguilar
2017-02-05 20:17 ` David Aguilar [this message]
2017-02-05 21:23 ` [PATCH] difftool: fix bug when printing usage David Aguilar
2017-02-06 16:58 ` Johannes Schindelin
2017-02-06 18:13 ` Junio C Hamano
2017-02-07 11:21 ` Johannes Schindelin
2017-02-07 20:03 ` Junio C Hamano
2017-02-07 20:06 ` Junio C Hamano
2017-02-08 15:06 ` 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=20170205201751.z4rfmy5xxaqg472l@gmail.com \
--to=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johannes.schindelin@gmx.de \
--cc=liu.denton@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).