Hello all,
Please see my comments below.
On 2024-04-17 00:31, Junio C Hamano wrote:
<rsbecker@xxxxxxxxxxxxx> writes:
I am having a bit of trouble understanding the use-case for
this. Is it limited to linkgit? Under what circumstances would I
need to use such capabilities?
When you run "git commit" from the command line without specifying
any message, you'd get an editor spawned for you with something like
this in the file ("--- >8 ---" and "--- 8< ---" are for illustration
purposes in this message).
--- >8 ---
# Please enter the commit message for your changes. Lines starting
# with '#' will be ignored, and an empty message aborts the commit.
#
# On branch next
# Untracked files:
# +runme.sh
# P
#
--- 8< ---
Frankly, I'd much rather see a new configuration option that would
suppress the two leading lines in the example above. Of course, they'd
still be displayed by default.
But when you run "git commit --cleanup=scissors" (or use the
equivalent configuration variables), you'd get this instead.
--- >8 ---
# ------------------------ >8 ------------------------
# Do not modify or remove the line above.
# Everything below it will be ignored.
#
# On branch next
# Untracked files:
# +runme.sh
# P
#
--- 8< ---
The new advice configuration is to suppress the two lines from that
message template.
I think this new configuration option might be useful to some users,
but I'd suggest that it gets extended to also suppress the two opening
lines mentioned in my comment on the first example above.
I agree that a bit more background information should be given in
the proposed log message to help readers. It should mention when
this new setting is relevant (e.g., when the "--cleanup=scissors"
option is in effect), at least.
I suspect that the same configuration variable wants to also control
the "helpful" comment in the "normal" case, in which case the name
of the configuration variable would need to be rethought.
Agreed, a better name for the new option would be helpful.
