[PATCH v4 0/3] handle empty spec-compliant remote repos correctly
- From
- Jonathan Tan <jonathantanmy@google.com>
- Date
- Sep 9, 2016, 17:36 UTC
- Message-ID
- <cover.1473441620.git.jonathantanmy@google.com>
- In-Reply-To
- <cover.1472836026.git.jonathantanmy@google.com>
Updates:
o Included tighten-check patch from Jonathan Nieder and Junio C Hamano
in this patch set
o Updated commit message following Jonathan Nieder's suggestion
o Updated warning messages to mention capabilities^{}As for warning vs die, I would prefer the "liberal" approach of continuing on when facing a recoverable error (that is, "warning"). But I agree that there are good points in favor of using fatal errors ("die") and I can switch to that if there is consensus.
Jonathan Nieder (1): connect: tighten check for unexpected early hang up
Jonathan Tan (2): tests: move test_lazy_prereq JGIT to test-lib.sh connect: advertized capability is not a ref
connect.c | 35 +++++++++++++++++++++++++++++------ t/t5310-pack-bitmaps.sh | 4 ---- t/t5512-ls-remote.sh | 40 ++++++++++++++++++++++++++++++++++++++++ t/test-lib.sh | 4 ++++ 4 files changed, 73 insertions(+), 10 deletions(-)
-- 2.8.0.rc3.226.g39d4020