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 12:44:33 -0700 [thread overview]
Message-ID: <xmqqecl6pe8u.fsf@gitster.g> (raw)
In-Reply-To: <8c9dd9f9-4d41-4901-b1fb-080e4e73b40a@app.fastmail.com> (Kristoffer Haugsbakk's message of "Thu, 26 Mar 2026 20:22:46 +0100")
"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:
> With git-name-rev(1) it looked like formatting options could crowd up
> the place.
>
>> Wouldn't this be done as a new option to "git log", for example?
>
> Okay with me.
>
> git-log(1) blocks until I have closed stdin and effectively dedups
> the output.
Ah, I forgot about the "--stdin" mode. That makes it a non-starter
X-<. Sorry about the noise.
>
> git log --oneline --stdin --no-walk
> HEAD
> HEAD
> HEAD
> ^D
> <HEAD is listed one time>
>
> So if an option could tweak it to instead (1) give one output per line
> (like git-name-rev(1)) and (2) not deduplicate (well, follows from (1))
> then the problem seems solved.
>
> Thinking out loud here.
next prev parent reply other threads:[~2026-03-26 19:44 UTC|newest]
Thread overview: 9+ 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 ` kh/name-rev-custom-format Junio C Hamano
2026-03-26 19:22 ` kh/name-rev-custom-format Kristoffer Haugsbakk
2026-03-26 19:44 ` Junio C Hamano [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-05-11 3:08 What's cooking in git.git (May 2026, #02) Junio C Hamano
2026-05-11 13:22 ` kh/name-rev-custom-format Kristoffer Haugsbakk
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=xmqqecl6pe8u.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 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.