summaryrefslogtreecommitdiff
path: root/t/t6016-rev-list-graph-simplify-history.sh
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2011-05-18 15:44:37 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2011-05-19 10:44:44 -0700
commitc3ab1a8e4cb8a84967efcf45c5e6bee41b17f9f9 (patch)
tree207ae18917753171c9e1125cf19446319ae8ecd8 /t/t6016-rev-list-graph-simplify-history.sh
parentUpdate release notes to 1.7.6 (diff)
downloadtgif-c3ab1a8e4cb8a84967efcf45c5e6bee41b17f9f9.tar.xz
notes remove: allow removing more than one
While "xargs -n1 git notes rm" is certainly a possible way to remove notes from many objects, this would create one notes "commit" per removal, which is not quite suitable for seasonal housekeeping. Allow taking more than one on the command line, and record their removal as a single atomic event if everthing goes well. Even though the old code insisted that "git notes rm" must be given only one object (or zero, in which case it would default to HEAD), this condition was not tested. Add tests to handle the new case where we feed multiple objects, and also make sure if there is a bad input, no change is recorded. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t6016-rev-list-graph-simplify-history.sh')
0 files changed, 0 insertions, 0 deletions