From: Manos Pitsidianakis <epilys@norn.io>
To: git@vger.kernel.org
Cc: me@ikke.info, sandals@crustytoothpaste.net, gitster@pobox.com,
peff@peff.net
Subject: [PATCH v3] log: forbid log --graph --no-walk
Date: Sun, 15 Mar 2015 02:43:14 +0200 [thread overview]
Message-ID: <5504D5A2.2070405@norn.io> (raw)
In-Reply-To: <md5:DbynqDqKsm8mpedJ3B12rw==>
In git-log, --graph shows a graphical representation of a continuous
commit history, and --no-walk shows discrete specified commits without
continuity. Using both doesn't make sense, so we forbid the combined use
of these flags.
Signed-off-by: Manos Pitsidianakis <epilys@norn.io>
---
This is a microproject intended to complement my GSoC application.
builtin/log.c | 2 ++
t/t4202-log.sh | 4 ++++
2 files changed, 6 insertions(+)
diff --git a/builtin/log.c b/builtin/log.c
index dd8f3fc..5aaf964 100644
--- a/builtin/log.c
+++ b/builtin/log.c
@@ -155,6 +155,8 @@ static void cmd_log_init_finish(int argc, const char **argv, const char *prefix,
memset(&w, 0, sizeof(w));
userformat_find_requirements(NULL, &w);
+ if (rev->graph && rev->no_walk)
+ die("--graph and --no-walk are incompatible");
if (!rev->show_notes_given && (!rev->pretty_given || w.notes))
rev->show_notes = 1;
if (rev->show_notes)
diff --git a/t/t4202-log.sh b/t/t4202-log.sh
index 5f2b290..5d72713 100755
--- a/t/t4202-log.sh
+++ b/t/t4202-log.sh
@@ -887,4 +887,8 @@ test_expect_success GPG 'log --graph --show-signature for merged tag' '
grep "^| | gpg: Good signature" actual
'
+test_expect_success 'forbid log --graph --no-walk' '
+ test_must_fail git log --graph --no-walk
+'
+
test_done
--
2.1.4
next parent reply other threads:[~2015-03-15 0:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <md5:DbynqDqKsm8mpedJ3B12rw==>
2015-03-15 0:43 ` Manos Pitsidianakis [this message]
2015-03-15 1:08 ` [PATCH v3] log: forbid log --graph --no-walk Dongcan Jiang
2015-03-15 1:24 ` Manos Pitsidianakis
2015-03-15 1:39 ` Dongcan Jiang
2015-03-16 19:00 ` Manos Pitsidianakis
2015-03-16 19:08 ` Junio C Hamano
2015-03-16 19:15 ` Manos Pitsidianakis
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=5504D5A2.2070405@norn.io \
--to=epilys@norn.io \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=me@ikke.info \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
/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).