4 Коммитов

Автор	SHA1	Сообщение	Дата
Jeff King	74eb32d3a4	receive-pack: drop "n/a" on unpacker errors ... The output from git push currently looks like this: $ git push dest HEAD fatal: [some message from index-pack] error: unpack failed: index-pack abnormal exit To dest ! [remote rejected] HEAD -> master (n/a (unpacker error)) That n/a is meant to be "the per-ref status is not available" but the nested parentheses just make it look ugly. Let's turn the final line into just: ! [remote rejected] HEAD -> master (unpacker error) Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>	2012-09-21 09:50:13 -07:00
Clemens Buchacher	ef7e93d908	do not override receive-pack errors ... Receive runs rev-list --verify-objects in order to detect missing objects. However, such errors are ignored and overridden later. Instead, consequently ignore all update commands for which an error has already been detected. Some tests in t5504 are obsoleted by this change, because invalid objects are detected even if fsck is not enabled. Instead, they now test for different error messages depending on whether or not fsck is turned on. A better fix would be to force a corruption that will be detected by fsck but not by rev-list. Signed-off-by: Clemens Buchacher <drizzd@aon.at> Signed-off-by: Junio C Hamano <gitster@pobox.com>	2012-02-13 13:29:08 -08:00
Junio C Hamano	2e2e7e9dd0	Merge branch 'jc/fetch-verify' ... * jc/fetch-verify: fetch: verify we have everything we need before updating our ref rev-list --verify-object list-objects: pass callback data to show_objects()	2011-10-05 12:36:20 -07:00
Junio C Hamano	b10a53583f	test: fetch/receive with fsckobjects ... Add tests for the new fetch.fsckobjects, and also tests for receive.fsckobjects we have had for quite some time. Signed-off-by: Junio C Hamano <gitster@pobox.com>	2011-09-04 18:19:36 -07:00