From: Junio C Hamano <gitster@pobox.com>
To: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
Cc: git@vger.kernel.org
Subject: Re: kh/name-rev-custom-format
Date: Thu, 26 Mar 2026 11:48:30 -0700 [thread overview]
Message-ID: <xmqqtsu2pgu9.fsf@gitster.g> (raw)
In-Reply-To: <e33142cb-1ec3-468f-8080-ba3bad79ae25@app.fastmail.com> (Kristoffer Haugsbakk's message of "Thu, 26 Mar 2026 19:07:57 +0100")
"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:
> On Wed, Mar 25, 2026, at 05:20, Junio C Hamano wrote:
>> * kh/name-rev-custom-format (2026-03-20) 2 commits
>> - name-rev: learn --format=<pretty>
>> - name-rev: wrap both blocks in braces
>>
>> "git name-rev" learned to use custom format instead of the object
>> name in an extended SHA-1 expression form.
>>
>> Comments?
>> source: <V2_CV_name-rev_--format.51b@msgid.xyz>
>
> I’m working on rewriting the functionality in the form of a new builtin
> git-format-rev(1) that lives in `builtin/name-rev.c`.
By the way, why do we want yet another builtin in the first place?
Wouldn't this be done as a new option to "git log", for example?
next prev parent reply other threads:[~2026-03-26 18:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 4:20 What's cooking in git.git (Mar 2026, #10) Junio C Hamano
2026-03-25 6:13 ` Jeff King
2026-03-25 8:33 ` Shreyansh Paliwal
2026-03-25 19:50 ` Junio C Hamano
2026-03-26 18:07 ` kh/name-rev-custom-format Kristoffer Haugsbakk
2026-03-26 18:48 ` Junio C Hamano [this message]
2026-03-26 19:22 ` kh/name-rev-custom-format Kristoffer Haugsbakk
2026-03-26 19:44 ` kh/name-rev-custom-format 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqtsu2pgu9.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=kristofferhaugsbakk@fastmail.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