summaryrefslogtreecommitdiff
path: root/t/t6009-rev-list-parent.sh
diff options
context:
space:
mode:
authorMichael J Gruber <git@drmicha.warpmail.net>2011-03-21 10:14:06 (GMT)
committerJunio C Hamano <gitster@pobox.com>2011-03-23 17:16:44 (GMT)
commitad5aeeded3295589b2573b143f754762a56f8f82 (patch)
tree264a93fc2b35d7e97ae4cd89b16d011cd4e149fa /t/t6009-rev-list-parent.sh
parent8ee50594889056322f2fc00a589a36e83b9119fd (diff)
downloadgit-ad5aeeded3295589b2573b143f754762a56f8f82.zip
git-ad5aeeded3295589b2573b143f754762a56f8f82.tar.gz
git-ad5aeeded3295589b2573b143f754762a56f8f82.tar.bz2
revision.c: introduce --min-parents and --max-parents options
Introduce --min-parents and --max-parents options which limit the revisions to those commits which have at least (or at most) that many commits, where negative arguments for --max-parents= denote infinity (i.e. no upper limit). In particular: --max-parents=1 is the same as --no-merges; --min-parents=2 is the same as --merges; --max-parents=0 shows only roots; and --min-parents=3 shows only octopus merges Using --min-parents=n and --max-parents=m with n>m gives you what you ask for (i.e. nothing) for obvious reasons, just like when you give --merges (show only merge commits) and --no-merges (show only non-merge commits) at the same time. Also, introduce --no-min-parents and --no-max-parents to do the obvious thing for convenience. We compute the number of parents only when we limit by that, so there is no performance impact when there are no limiters. Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t6009-rev-list-parent.sh')
0 files changed, 0 insertions, 0 deletions