aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2007-08-30 22:58:26 -0700
committerJunio C Hamano <gitster@pobox.com>2007-08-31 00:26:41 -0700
commita65f2005a6819d154172b01842eb39bd306a22cd (patch)
treebb737e6b03692380d5ed0a313254773d2817c27d
parent75d244990364e322e87e2549846b17252f440627 (diff)
downloadgit-a65f2005a6819d154172b01842eb39bd306a22cd.tar.gz
git-a65f2005a6819d154172b01842eb39bd306a22cd.tar.xz
Make "git-log --" without paths behave the same as "git-log" without --
"git log" family of commands, even when run from a subdirectory, do not limit the revision range with the current directory as the path limiter, but with double-dash without any paths after it, i.e. "git log --" do so. It was a mistake to have a difference between "git log --" and "git log" introduced in commit ae563542bf10fa8c33abd2a354e4b28aca4264d7 (First cut at libifying revlist generation). Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rw-r--r--revision.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/revision.c b/revision.c
index 51fff0ec5..c193c3ea2 100644
--- a/revision.c
+++ b/revision.c
@@ -896,7 +896,8 @@ int setup_revisions(int argc, const char **argv, struct rev_info *revs, const ch
continue;
argv[i] = NULL;
argc = i;
- revs->prune_data = get_pathspec(revs->prefix, argv + i + 1);
+ if (argv[i + 1])
+ revs->prune_data = get_pathspec(revs->prefix, argv + i + 1);
seen_dashdash = 1;
break;
}