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

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

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Sep 9, 2016, 21:07 UTC
Message-ID
<20160909210757.GH25016@google.com>
In-Reply-To
<cover.1473452153.git.jonathantanmy@google.com>
Jonathan Tan wrote:
Show 5 quoted lines
>  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(-)
Reviewed-by: Jonathan Nieder <jrnieder@gmail.com>

Thank you, Jonathan

Previous: Jonathan Tan
Message 5 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.