From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Beat Bolli <dev+git@drbeat.li>, Denton Liu <liu.denton@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH] pretty: allow to override the built-in formats
Date: Wed, 9 Sep 2020 05:08:42 -0400 [thread overview]
Message-ID: <20200909090842.GA2496536@coredump.intra.peff.net> (raw)
In-Reply-To: <xmqqzh60xhms.fsf@gitster.c.googlers.com>
On Tue, Sep 08, 2020 at 11:12:11AM -0700, Junio C Hamano wrote:
> > Here's a slightly different proposal. I'm not sure if I like it or not,
> > but just thinking out loud for a moment. The issue is that we're worried
> > the consumer of the output may be surprised by a user-configured pretty
> > format. Can we give them a way to say "I don't care about the exact
> > output; pick what the user configured for this name, or some sane
> > default". I.e., something like:
> >
> > git log --format=loose:reference
>
> Yeah, that, or with s/loose/user/ or something.
Heh, I actually called it "user:" initially but wasn't sure if that was
sufficiently descriptive, so I groped around for another word. But if
both of us thought of "user", maybe it's better.
At any rate, this was mostly just thinking out loud, and isn't something
I'm planning to follow up on with a patch. But maybe it inspires
somebody to run with it.
-Peff
next prev parent reply other threads:[~2020-09-09 9:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-05 19:24 [PATCH] pretty: allow to override the built-in formats Beat Bolli
2020-09-05 19:52 ` Denton Liu
2020-09-06 21:59 ` Junio C Hamano
2020-09-07 5:36 ` Beat Bolli
2020-09-07 6:54 ` Junio C Hamano
2020-09-07 7:06 ` Beat Bolli
2020-09-08 13:53 ` Jeff King
2020-09-08 18:12 ` Junio C Hamano
2020-09-09 9:08 ` Jeff King [this message]
2020-09-09 18:27 ` Junio C Hamano
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=20200909090842.GA2496536@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=dev+git@drbeat.li \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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.
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).