git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Derrick Stolee <stolee@gmail.com>
Cc: Robert Karszniewicz <avoidr@posteo.de>, git@vger.kernel.org
Subject: Re: [RFC PATCH] log: add log.showStat configuration variable
Date: Mon, 12 Oct 2020 09:14:31 -0700	[thread overview]
Message-ID: <xmqqtuuzqv4o.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <1f53a7d8-6aa5-e1c7-ecb9-b99a37500034@gmail.com> (Derrick Stolee's message of "Mon, 12 Oct 2020 08:50:35 -0400")

Derrick Stolee <stolee@gmail.com> writes:

>> I worried about that, too. But I think the initial step was already in
>> 2015, when stash.showStat and stash.showPatch were added. No flood of
>> options happened since then? I was actually surprised about it, too,
>> that it took so long until someone wanted to have showStat for show and
>> log, too.
>
> I'm not sure these examples will help your case.
>
> Does 'stash' have more things that would be beneficial to show
> every time? If no, then 'stash' is much more specialized than
> 'show' and 'log' which have many more options. If yes, then this
> is exactly what we want to avoid happening: an incomplete set of
> config options that are tailored to a small subset of options.

Well said---I do not have anything more to add to that point that
'stash' is not a very good example to mimic.

      reply	other threads:[~2020-10-12 16:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-08 16:20 [RFC PATCH] log: add log.showStat configuration variable Robert Karszniewicz
2020-10-08 17:58 ` Junio C Hamano
2020-10-10 14:02   ` Robert Karszniewicz
2020-10-08 18:12 ` Derrick Stolee
2020-10-11  9:59   ` Robert Karszniewicz
2020-10-12 12:50     ` Derrick Stolee
2020-10-12 16:14       ` Junio C Hamano [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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqtuuzqv4o.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=avoidr@posteo.de \
    --cc=git@vger.kernel.org \
    --cc=stolee@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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).