From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
To: "Henry Qin" <root@hq6.me>, git@vger.kernel.org
Subject: Re: Feature Request: Document the log format string equivalent of built-in formats
Date: Tue, 15 Oct 2024 20:04:58 +0200 [thread overview]
Message-ID: <22391e5d-c6fa-4b33-a12a-b63bbb979d81@app.fastmail.com> (raw)
In-Reply-To: <CAO8bsPCWkqDFSqWwJ3gQt7O2g1okodb_Q-NbbkTq9bc7M=zU1A@mail.gmail.com>
Backlink:
https://stackoverflow.com/questions/79089206/is-it-possible-to-fully-replicate-the-default-behavior-of-git-log-with-a-format
I took a look at the code before today with search terms like
CMIT_FMT_DEFAULT
CMIT_FMT_MEDIUM,
And it looked to me that at least parts of it were implemented using
regular code branching. I was thinking that maybe the built-in formats
were defined just using the formatting primitives. But it didn’t look
like that to me.
next prev parent reply other threads:[~2024-10-15 18:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 17:31 Feature Request: Document the log format string equivalent of built-in formats Henry Qin
2024-10-15 18:04 ` Kristoffer Haugsbakk [this message]
2024-10-15 18:43 ` Henry Qin
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=22391e5d-c6fa-4b33-a12a-b63bbb979d81@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail.com \
--cc=git@vger.kernel.org \
--cc=root@hq6.me \
/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