From: Namhyung Kim <namhyung@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] stash: Add stash.showFlag config variable
Date: Fri, 28 Aug 2015 10:54:33 +0900 [thread overview]
Message-ID: <20150828015433.GB17656@sejong> (raw)
In-Reply-To: <xmqq614043u0.fsf@gitster.mtv.corp.google.com>
Hi,
On Thu, Aug 27, 2015 at 06:08:39PM -0700, Junio C Hamano wrote:
> Namhyung Kim <namhyung@gmail.com> writes:
>
> > +stash.showFlag::
> > + The default option to pass to `git stash show` when no option is
> > + given. The default is '--stat'. See description of 'show' command
> > + in linkgit:git-stash[1].
>
> Doesn't the same discussion in $gmane/275752 apply here? By
> designing the configuration variable in a sloppy way, this change
> will force us to spawn "git diff" via the shell forever, even after
> somebody ports "git stash" to C.
>
> Which is not great.
I see.
>
> Perhaps a pair of new booleans
>
> - stash.showStat (defaults to true but you can turn it off)
> - stash.showPatch (defaults to false but you can turn it on)
>
> or something along that line might be sufficient and more palatable.
Hmm.. I agree with you, but I don't know what we should do if both of
the options were off. Just run 'git diff' with no option is ok to you?
>
> I dunno.
:)
>
>
> [Footnote]
>
> *1* Besides, showFlag is a strange configuration variable name. I
> thought that by setting it to true, you are making "git stash"
> command to somehow show some kind of a flag when it does its
> operation ;-).
I admit that it's a bad name. My naming sense is always horrible.. ;-p
Thanks for the review!
Namhyung
next prev parent reply other threads:[~2015-08-28 2:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 13:52 [PATCH] stash: Add stash.showFlag config variable Namhyung Kim
2015-08-27 15:20 ` SZEDER Gábor
2015-08-27 15:36 ` Namhyung Kim
2015-08-28 0:16 ` Eric Sunshine
2015-08-28 1:47 ` Namhyung Kim
2015-08-28 1:08 ` Junio C Hamano
2015-08-28 1:54 ` Namhyung Kim [this message]
2015-08-28 18:10 ` Junio C Hamano
2015-08-29 15:19 ` Namhyung Kim
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=20150828015433.GB17656@sejong \
--to=namhyung@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).