git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Beat Bolli <dev+git@drbeat.li>
To: git@vger.kernel.org
Cc: gitster@pobox.com, Beat Bolli <dev+git@drbeat.li>
Subject: [PATCH] pretty: allow to override the built-in formats
Date: Sat,  5 Sep 2020 21:24:06 +0200	[thread overview]
Message-ID: <20200905192406.74411-1-dev+git@drbeat.li> (raw)

In 1f0fc1db8599 (pretty: implement 'reference' format, 2019-11-19), the
"reference" format was added. As a built-in format, it cannot be
overridden, although different projects may have divergent conventions
on how to format a commit reference. E.g., Git uses

    <hash> (<subject>, <short-date>) [1]

while Linux uses

    <hash> ("<subject>") [2]

Teach pretty to look at a different set of config variables, all
starting with "override" (e.g. "pretty.overrideReference"), to override
the built-in formats. Note that a format called "override" by itself is
not affected. The prefix was chosen to make it clear to the user that
this should not be done without thought, as it may cause issues with
other tools that expect the built-in formats to be immutable.

[1] https://github.com/git/git/blob/3a238e539bcdfe3f9eb5010fd218640c1b499f7a/Documentation/SubmittingPatches#L144
[2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v5.9-rc3#n167

Signed-off-by: Beat Bolli <dev+git@drbeat.li>
---
I intend to also submit a patch to gitk that will use "git show -s
--pretty=reference" if it is available, with a fallback to reading
"pretty.overrideReference", so there's a single point of configuration
for the reference format.

 Documentation/config/pretty.txt |  6 ++++--
 pretty.c                        | 20 +++++++++++++++-----
 t/t4205-log-pretty-formats.sh   |  8 ++++++++
 3 files changed, 27 insertions(+), 7 deletions(-)

diff --git a/Documentation/config/pretty.txt b/Documentation/config/pretty.txt
index 063c6b63d9..d9dac7b3ee 100644
--- a/Documentation/config/pretty.txt
+++ b/Documentation/config/pretty.txt
@@ -5,5 +5,7 @@ pretty.<name>::
 	running `git config pretty.changelog "format:* %H %s"`
 	would cause the invocation `git log --pretty=changelog`
 	to be equivalent to running `git log "--pretty=format:* %H %s"`.
-	Note that an alias with the same name as a built-in format
-	will be silently ignored.
+	Note that you can override a built-in format by prefixing its
+	name with `override`, e.g. `pretty.overrideReference` to override
+	the built-in reference format. Doing so can cause interoperability
+	issues with tools that expect a built-in format to be immutable.
diff --git a/pretty.c b/pretty.c
index 2a3d46bf42..a8f8ade470 100644
--- a/pretty.c
+++ b/pretty.c
@@ -46,18 +46,28 @@ static int git_pretty_formats_config(const char *var, const char *value, void *c
 {
 	struct cmt_fmt_map *commit_format = NULL;
 	const char *name;
+	const char *suffix;
 	const char *fmt;
 	int i;
 
 	if (!skip_prefix(var, "pretty.", &name))
 		return 0;
-
-	for (i = 0; i < builtin_formats_len; i++) {
-		if (!strcmp(commit_formats[i].name, name))
-			return 0;
+	if (skip_prefix(name, "override", &suffix) && *suffix) {
+		name = suffix;
+		/* also search the built-in formats */
+		i = 0;
+	} else {
+		for (i = 0; i < builtin_formats_len; i++) {
+			if (!strcmp(commit_formats[i].name, name))
+				return 0;
+		}
+		/*
+		 * Here, i == builtin_formats_len, so we only search the
+		 * user-defined formats
+		 */
 	}
 
-	for (i = builtin_formats_len; i < commit_formats_len; i++) {
+	for (; i < commit_formats_len; i++) {
 		if (!strcmp(commit_formats[i].name, name)) {
 			commit_format = &commit_formats[i];
 			break;
diff --git a/t/t4205-log-pretty-formats.sh b/t/t4205-log-pretty-formats.sh
index 204c149d5a..55c37be392 100755
--- a/t/t4205-log-pretty-formats.sh
+++ b/t/t4205-log-pretty-formats.sh
@@ -52,6 +52,14 @@ test_expect_success 'alias masking builtin format' '
 	test_cmp expected actual
 '
 
+test_expect_success 'overriding builtin format' '
+	git log --pretty=%H >expected &&
+	git config pretty.overrideOneline "%H" &&
+	git log --pretty=oneline >actual &&
+	git config --unset pretty.overrideOneline &&
+	test_cmp expected actual
+'
+
 test_expect_success 'alias user-defined format' '
 	git log --pretty="format:%h" >expected &&
 	git config pretty.test-alias "format:%h" &&
-- 
2.26.0.277.gb8618d28a9


             reply	other threads:[~2020-09-05 19:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-05 19:24 Beat Bolli [this message]
2020-09-05 19:52 ` [PATCH] pretty: allow to override the built-in formats Denton Liu
2020-09-06 21:59   ` Junio C Hamano
2020-09-07  5:36     ` Beat Bolli
2020-09-07  6:54       ` Junio C Hamano
2020-09-07  7:06         ` Beat Bolli
2020-09-08 13:53         ` Jeff King
2020-09-08 18:12           ` Junio C Hamano
2020-09-09  9:08             ` Jeff King
2020-09-09 18:27               ` Junio C Hamano

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200905192406.74411-1-dev+git@drbeat.li \
    --to=dev+git@drbeat.li \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).