From: Junio C Hamano <gitster@pobox.com>
To: "Nuno Sá" <noname.nuno@gmail.com>
Cc: Erik Cervin Edin <erik@cervined.in>, git@vger.kernel.org
Subject: Re: git notes question
Date: Thu, 10 Mar 2022 09:52:01 -0800 [thread overview]
Message-ID: <xmqqlexhg0fy.fsf@gitster.g> (raw)
In-Reply-To: <f5be5b264f30f689546db3883b4b64c88ba00cb3.camel@gmail.com> ("Nuno Sá"'s message of "Thu, 10 Mar 2022 09:37:18 +0100")
Nuno Sá <noname.nuno@gmail.com> writes:
>> Well, this time it was "Notes:" label, but the next person who
>> wants to see a deviation from the canned "email" format would want a
>> deviation different from yours. Perhaps they want a different way
>
> I'm surely missing something but I'm not sure this is specific to the
> email format? It's just that git-notes by default will always either
> append the "Notes:" or "Notes (<refname>):" independent of the
> predefined format you use. The only way to stop it from doing that is,
> apparently, by using your own --format=<template>...
> ...
> What I was asking was just if there was a way to not use these default
> strings. I don't think this would open all kind of deviations.
Not limited to the email format. "git log" will always prefix
"Author: " before the commit author name, "Date: " date with extra
paddingbefore the author, indents the log message by 4 spaces, adds
"Notes (refname):" before notes, and indentation is given before the
contents of the notes. There are many things, other than the
presence of the "Notes" label, that people may want to customize in
the output from the commands in the "git log" family, including "git
format-patch".
I think you were too focused on "Notes" tree to lose the view of the
forest. A line is drawn not to special case "Notes" prefix, because
there is no reason to do so without allowing all other things to
also be tweaked, and it will "open all kind of deviations".
next prev parent reply other threads:[~2022-03-10 17:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 13:08 git notes question Nuno Sá
2022-03-09 8:54 ` Erik Cervin Edin
2022-03-09 9:11 ` Nuno Sá
2022-03-09 18:02 ` Junio C Hamano
2022-03-10 8:37 ` Nuno Sá
2022-03-10 13:11 ` Erik Cervin Edin
2022-03-10 13:26 ` Nuno Sá
2022-03-10 17:52 ` Junio C Hamano [this message]
2022-03-11 9:02 ` Nuno Sá
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=xmqqlexhg0fy.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=erik@cervined.in \
--cc=git@vger.kernel.org \
--cc=noname.nuno@gmail.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;
as well as URLs for NNTP newsgroup(s).