From: Alex Henrie <alexhenrie24@gmail.com>
To: git@vger.kernel.org, paulus@ozlabs.org
Cc: Alex Henrie <alexhenrie24@gmail.com>
Subject: [PATCH 2/3] log: add a config option for --graph
Date: Wed, 9 Feb 2022 09:23:48 -0700 [thread overview]
Message-ID: <20220209162350.169971-2-alexhenrie24@gmail.com> (raw)
In-Reply-To: <20220209162350.169971-1-alexhenrie24@gmail.com>
A coworker recently asked me how to turn on --graph by default in
`git log`. I googled it and found that several people have asked that
before on Stack Overflow, with no good solution:
https://stackoverflow.com/questions/43555256/how-do-i-make-git-log-graph-the-default
Add a log.graph option to turn on graph mode in the absence of any
incompatible options.
It would be nice to have a --no-graph command line option to countermand
log.graph=true, but it's not clear how that would work with topo_order
and rewrite_parents, which can be set by other options. In any case, it
is still possible to countermand log.graph=true per invocation with
`git -c log.graph=false log`.
Signed-off-by: Alex Henrie <alexhenrie24@gmail.com>
---
Documentation/config/log.txt | 5 +++++
Documentation/git-log.txt | 5 +++++
builtin/log.c | 17 +++++++++++++++++
t/t4202-log.sh | 35 +++++++++++++++++++++++++++++++++++
4 files changed, 62 insertions(+)
diff --git a/Documentation/config/log.txt b/Documentation/config/log.txt
index 456eb07800..3e356cfce6 100644
--- a/Documentation/config/log.txt
+++ b/Documentation/config/log.txt
@@ -35,6 +35,11 @@ log.follow::
i.e. it cannot be used to follow multiple files and does not work well
on non-linear history.
+log.graph::
+ If true, makes linkgit:git-log[1], linkgit:git-show[1], and
+ linkgit:git-whatchanged[1] assume `--graph` unless an incompatible
+ option is also specified.
+
log.graphColors::
A list of colors, separated by commas, that can be used to draw
history lines in `git log --graph`.
diff --git a/Documentation/git-log.txt b/Documentation/git-log.txt
index 20e87cecf4..7e9e0f8afe 100644
--- a/Documentation/git-log.txt
+++ b/Documentation/git-log.txt
@@ -214,6 +214,11 @@ log.follow::
i.e. it cannot be used to follow multiple files and does not work well
on non-linear history.
+log.graph::
+ If `true`, `git log` and related commands will act as if the
+ `--graph` option was passed to them unless an incompatible option is
+ also specified.
+
log.showRoot::
If `false`, `git log` and related commands will not treat the
initial commit as a big creation event. Any root commits in
diff --git a/builtin/log.c b/builtin/log.c
index 4b493408cc..1f0db54c84 100644
--- a/builtin/log.c
+++ b/builtin/log.c
@@ -35,6 +35,7 @@
#include "repository.h"
#include "commit-reach.h"
#include "range-diff.h"
+#include "graph.h"
#define MAIL_DEFAULT_WRAP 72
#define COVER_FROM_AUTO_MAX_SUBJECT_LEN 100
@@ -48,6 +49,7 @@ static int default_show_root = 1;
static int default_follow;
static int default_show_signature;
static int default_encode_email_headers = 1;
+static int default_graph;
static int decoration_style;
static int decoration_given;
static int use_mailmap_config = 1;
@@ -234,6 +236,17 @@ static void cmd_log_init_finish(int argc, const char **argv, const char *prefix,
read_mailmap(rev->mailmap);
}
+ if (default_graph &&
+ !rev->graph &&
+ !rev->track_linear &&
+ !rev->reverse &&
+ !rev->reflog_info &&
+ !rev->no_walk) {
+ rev->topo_order = 1;
+ rev->rewrite_parents = 1;
+ rev->graph = graph_init(rev);
+ }
+
if (rev->pretty_given && rev->commit_format == CMIT_FMT_RAW) {
/*
* "log --pretty=raw" is special; ignore UI oriented
@@ -519,6 +532,10 @@ static int git_log_config(const char *var, const char *value, void *cb)
default_show_signature = git_config_bool(var, value);
return 0;
}
+ if (!strcmp(var, "log.graph")) {
+ default_graph = git_config_bool(var, value);
+ return 0;
+ }
if (grep_config(var, value, cb) < 0)
return -1;
diff --git a/t/t4202-log.sh b/t/t4202-log.sh
index 5049559861..3b6f7aff23 100755
--- a/t/t4202-log.sh
+++ b/t/t4202-log.sh
@@ -1671,6 +1671,41 @@ test_expect_success 'log --graph with --name-only' '
test_cmp_graph --name-only tangle..reach
'
+test_expect_success 'log.graph=true behaves like --graph' '
+ git log --graph >expect &&
+ test_config log.graph true &&
+ git log >actual &&
+ test_cmp expect actual
+'
+
+test_expect_success '--show-linear-break ignores log.graph' '
+ git log --show-linear-break >expect &&
+ test_config log.graph true &&
+ git log --show-linear-break >actual &&
+ test_cmp expect actual
+'
+
+test_expect_success '--reverse ignores log.graph' '
+ git log --reverse >expect &&
+ test_config log.graph true &&
+ git log --reverse >actual &&
+ test_cmp expect actual
+'
+
+test_expect_success '--walk-reflogs ignores log.graph' '
+ git log --walk-reflogs >expect &&
+ test_config log.graph true &&
+ git log --walk-reflogs >actual &&
+ test_cmp expect actual
+'
+
+test_expect_success '--no-walk ignores log.graph' '
+ git log --no-walk >expect &&
+ test_config log.graph true &&
+ git log --no-walk >actual &&
+ test_cmp expect actual
+'
+
test_expect_success 'dotdot is a parent directory' '
mkdir -p a/b &&
( echo sixth && echo fifth ) >expect &&
--
2.32.0.2645.gc109162a1f
next prev parent reply other threads:[~2022-02-09 16:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 16:23 [PATCH 1/3] log: fix memory leak if --graph is passed multiple times Alex Henrie
2022-02-09 16:23 ` Alex Henrie [this message]
2022-02-09 18:25 ` [PATCH 2/3] log: add a config option for --graph Junio C Hamano
2022-02-10 16:49 ` Alex Henrie
2022-02-09 16:23 ` [PATCH 3/3] gitk: set log.graph=false when running `git log` Alex Henrie
2022-02-09 18:26 ` Junio C Hamano
2022-02-10 16:50 ` Alex Henrie
2022-02-10 20:15 ` Junio C Hamano
2022-02-09 18:16 ` [PATCH 1/3] log: fix memory leak if --graph is passed multiple times 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=20220209162350.169971-2-alexhenrie24@gmail.com \
--to=alexhenrie24@gmail.com \
--cc=git@vger.kernel.org \
--cc=paulus@ozlabs.org \
/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).