From: Junio C Hamano <gitster@pobox.com>
To: "James Liu" <james@jamesliu.io>
Cc: <git@vger.kernel.org>
Subject: Re: [PATCH 0/1] log: make the --oneline option work with -L
Date: Wed, 13 Mar 2024 15:47:17 -0700 [thread overview]
Message-ID: <xmqqfrwt696y.fsf@gitster.g> (raw)
In-Reply-To: <CZSZ38DTWF14.3BNXFKTGVPLZQ@jamesliu.io> (James Liu's message of "Thu, 14 Mar 2024 09:24:22 +1100")
"James Liu" <james@jamesliu.io> writes:
> I suppose it isn't intuitive to me which options affect how the commits
> are presented, and which affect the diffs. The help entry for -L states
> that it will "Trace the evolution of the line range", which doesn't
> immediately suggest that it tweaks how the log message is shown.
Sorry, but you lost me. I do not understand this remark.
The documentation for "-L" does not talk about tweaking how the
message is shown at all, because "-L" does not have a say in how the
log message gets shown at all. And the documentation for
"--oneline", "--format", "--pretty" all should talk about how the
log message gets shown.
Anyway, if you are happy with "--no-patch", that's good.
prev parent reply other threads:[~2024-03-13 22:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 9:08 [PATCH 0/1] log: make the --oneline option work with -L James Liu
2024-03-13 9:08 ` [PATCH 1/1] log: ensure diffs are omitted with --oneline James Liu
2024-03-13 17:31 ` [PATCH 0/1] log: make the --oneline option work with -L Junio C Hamano
2024-03-13 18:08 ` Beat Bolli
2024-03-13 22:25 ` James Liu
2024-03-13 22:24 ` James Liu
2024-03-13 22:47 ` 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=xmqqfrwt696y.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=james@jamesliu.io \
/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.