| commit | 0c62705a0d9730df027a4e4074a8d9d5293e0b9b | |
| author | Michele Ballabio <barra_cuda@katamail.com> | |
| Sun, 23 Mar 2008 21:34:34 +0000 (23 22:34 +0100) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Thu, 27 Mar 2008 20:55:15 +0000 (27 13:55 -0700) | ||
| tree | 19fef6a279c19a396b67975cd1ec17eb2d223eef | treesnapshot (tar.gz zip) |
| parent | 1f4a711a05e00db81da552dd990f6ddff4ffb63e | commitdiff |
Add tests for git-prune
It seems that git prune changed behaviour with respect to revisions added
from command line, probably when it became a builtin. Currently, it prints
a short usage and exits: instead, it should take those revisions into
account and not prune them. So add a couple of test to point this out.
We'll be fixing this by switching to parse_options(), so add tests to
detect bogus command line parameters as well, to keep ourselves from
introducing regressions.
Signed-off-by: Michele Ballabio <barra_cuda@katamail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
It seems that git prune changed behaviour with respect to revisions added
from command line, probably when it became a builtin. Currently, it prints
a short usage and exits: instead, it should take those revisions into
account and not prune them. So add a couple of test to point this out.
We'll be fixing this by switching to parse_options(), so add tests to
detect bogus command line parameters as well, to keep ourselves from
introducing regressions.
Signed-off-by: Michele Ballabio <barra_cuda@katamail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| t/t5304-prune.sh | diffblobblamehistory |