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>
This commit is contained in:
Junio C Hamano 2005-08-08 19:31:37 -07:00
Родитель 76cd8eb619
Коммит 5ccfb758b0
1 изменённых файлов: 3 добавлений и 0 удалений

Просмотреть файл

@ -33,6 +33,9 @@ static int is_rev_argument(const char *arg)
"--max-age=",
"--min-age=",
"--merge-order",
"--topo-order",
"--bisect",
"--no-merges",
NULL
};
const char **p = rev_args;