From: Junio C Hamano <gitster@pobox.com>
To: Ben Knoble <ben.knoble@gmail.com>
Cc: "Jelle van der Waa" <jelle@vdwaa.nl>,
"Karthik Nayak" <karthik.188@gmail.com>,
"Phillip Wood" <phillip.wood123@gmail.com>,
git@vger.kernel.org, "Patrick Steinhardt" <ps@pks.im>,
"Phillip Wood" <phillip.wood@dunelm.org.uk>,
"Harald Nordgren" <haraldnordgren@gmail.com>,
"René Scharfe" <l.s.r@web.de>
Subject: Re: [RFC PATCH 0/2] Support --verbose in git history
Date: Mon, 16 Nov 2026 19:29:07 -0800 [thread overview]
Message-ID: <xmqqik1wgmpo.fsf@gitster.g> (raw)
In-Reply-To: <AC0A5AE7-B385-444B-B341-2738992D8C77@gmail.com> (Ben Knoble's message of "Mon, 16 Nov 2026 21:33:30 -0500")
Ben Knoble <ben.knoble@gmail.com> writes:
>> Le 16 nov. 2026 à 14:23, Jelle van der Waa <jelle@vdwaa.nl> a écrit :
>
>
>> I'll spin up a new patch which will drop the --verbose option and make "verbose" follow commit.verbose and make it the default for git history.
>
> Even with a config setting, we’d still want a CLI option to behave
> deterministically for interactive use (or for scripts), no?
Absolutely. Also, isn't the opposite of '--verbose' '--quiet'?
Or OPT__VERBOSITY()?
prev parent reply other threads:[~2026-11-17 3:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 19:30 [RFC PATCH 0/2] Support --verbose in git history Jelle van der Waa
2026-11-07 19:30 ` [RFC PATCH 1/2] history: drop redundant strbuf_stripspace() Jelle van der Waa
2026-11-07 19:30 ` [RFC PATCH 2/2] history: add --verbose option for reword Jelle van der Waa
2026-11-09 10:17 ` Phillip Wood
2026-11-07 19:49 ` [RFC PATCH 0/2] Support --verbose in git history D. Ben Knoble
2026-11-09 10:18 ` Phillip Wood
2026-11-09 12:06 ` Karthik Nayak
2026-11-09 12:43 ` D. Ben Knoble
2026-11-09 14:14 ` Phillip Wood
2026-11-10 13:13 ` Karthik Nayak
2026-11-10 17:15 ` Ben Knoble
2026-11-11 10:46 ` Patrick Steinhardt
2026-11-11 13:57 ` Phillip Wood
2026-11-11 14:03 ` Patrick Steinhardt
2026-11-11 15:39 ` Ben Knoble
2026-11-11 16:07 ` Patrick Steinhardt
2026-11-16 19:23 ` Jelle van der Waa
2026-11-17 2:33 ` Ben Knoble
2026-11-17 3:29 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqik1wgmpo.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=ben.knoble@gmail.com \
--cc=git@vger.kernel.org \
--cc=haraldnordgren@gmail.com \
--cc=jelle@vdwaa.nl \
--cc=karthik.188@gmail.com \
--cc=l.s.r@web.de \
--cc=phillip.wood123@gmail.com \
--cc=phillip.wood@dunelm.org.uk \
--cc=ps@pks.im \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.