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

Re: [PATCH] builtin/ls-remote: fall back to SHA1 outside of a repo

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 2, 2024, 15:26 UTC
Message-ID
<xmqqle1feyiy.fsf@gitster.g>
In-Reply-To
<c52112d3946b2fd8d030580cd7acb809fa54012a.1722573777.git.ps@pks.im>
Patrick Steinhardt <ps@pks.im> writes:
> I didn't spot this in the "What's cooking" report. I guess that's my own
> fault for not sending it as a proper patch, so let me fix that now :)

Yeah, I had a fix already when I gave my response to the initial problem report, but felt that it was too premature to commit to the approach before listening to others (you included) for potentially better alternative approaches, and then forgot about it.

The fix here is in line with my thoughts, after seeing how other parts of the transport work. Thanks for tying the loose ends.

Previous: Patrick Steinhardt
Message 6 of 6 in “[2.46 regression] git ls-remote crash with import remote-helper”
  1. Mike HommeyJul 27, 2024
  2. Junio C HamanoJul 28, 2024
  3. Patrick SteinhardtJul 29, 2024
  4. Junio C HamanoJul 29, 2024
  5. builtin/ls-remote: fall back to SHA1 outside of a repoPatrick Steinhardt, Aug 2, 2024
  6. Junio C HamanoAug 2, 2024

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.