summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 76cd8eb)
raw | patch | inline | side by side (parent: 76cd8eb)
author | Junio C Hamano <junkio@cox.net> | |
Tue, 9 Aug 2005 02:31:37 +0000 (19:31 -0700) | ||
committer | Junio C Hamano <junkio@cox.net> | |
Wed, 10 Aug 2005 05:28:21 +0000 (22:28 -0700) |
I haven't audited the rev-parse users, but I am having a feeling
that many of them would choke when they expect a couple of SHA1
object names and malicious user feeds them "--max-count=6" or
somesuch to shoot himself in the foot. Anyway, this adds a
couple of missing parameters that affect the list of revs to be
returned from rev-list, not the flags that affect how they are
presented by rev-list. I think that is the intention, but I am
not quite sure.
Signed-off-by: Junio C Hamano <junkio@cox.net>
that many of them would choke when they expect a couple of SHA1
object names and malicious user feeds them "--max-count=6" or
somesuch to shoot himself in the foot. Anyway, this adds a
couple of missing parameters that affect the list of revs to be
returned from rev-list, not the flags that affect how they are
presented by rev-list. I think that is the intention, but I am
not quite sure.
Signed-off-by: Junio C Hamano <junkio@cox.net>
rev-parse.c | patch | blob | history |
diff --git a/rev-parse.c b/rev-parse.c
index 1965e90a8a0c3fa25c2fccfcc82f5da395a093bc..1c6ae76f9aa32dab77a4189a4ae6b744d39cee36 100644 (file)
--- a/rev-parse.c
+++ b/rev-parse.c
"--max-age=",
"--min-age=",
"--merge-order",
+ "--topo-order",
+ "--bisect",
+ "--no-merges",
NULL
};
const char **p = rev_args;