git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH v5 0/3] handle empty spec-compliant remote repos correctly

From
JTJonathan Tan <jonathantanmy@google.com>
Date
Sep 9, 2016, 20:17 UTC
Message-ID
<cover.1473452153.git.jonathantanmy@google.com>
In-Reply-To
<cover.1472836026.git.jonathantanmy@google.com>
Updates from PATCH v4:
o use fatal errors ("die") instead of warnings for protocol errors
o reworded commit message - removed last sentence and wrote "(following the
  specification in pack-protocol.txt)" in one of the earlier paragraphs
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               | 32 ++++++++++++++++++++++++++------
 t/t5310-pack-bitmaps.sh |  4 ----
 t/t5512-ls-remote.sh    | 40 ++++++++++++++++++++++++++++++++++++++++
 t/test-lib.sh           |  4 ++++
 4 files changed, 70 insertions(+), 10 deletions(-)
-- 
2.8.0.rc3.226.g39d4020
Next: Jonathan Tan
Message 1 of 5 in “handle empty spec-compliant remote repos correctly”
  1. 0/3 handle empty spec-compliant remote repos correctlyJonathan Tan, Sep 9, 2016
  2. 2/3 connect: tighten check for unexpected early hang upJonathan Tan, Sep 9, 2016
  3. 1/3 tests: move test_lazy_prereq JGIT to test-lib.shJonathan Tan, Sep 9, 2016
  4. 3/3 connect: advertized capability is not a refJonathan Tan, Sep 9, 2016
  5. Jonathan NiederSep 9, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.