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

Re: [PATCH] archive: let remote clients get reachable commits

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 22, 2013, 18:06 UTC
Message-ID
<7vfw0odxz3.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20130222172710.GB17475@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
> How are you proposing to verify master~12 in that example? Because
> during parsing, it starts with "master", and we remember that?

By not cheating (i.e. using get_sha1()), but making sure you can parse "master" and the adornment on it "~12" is something sane.

That is why I said "this is harder than one would naively think, but limiting will make it significantly easier". I didn't say that it would become "trivial", did I?

Previous: Jeff KingNext: Jeff King
Message 5 of 7 in “archive: let remote clients get reachable commits”
  1. archive: let remote clients get reachable commitsSergey Segeev, Feb 21, 2013
  2. Jeff KingFeb 21, 2013
  3. Junio C HamanoFeb 22, 2013
  4. Jeff KingFeb 22, 2013
  5. Junio C HamanoFeb 22, 2013
  6. Jeff KingFeb 22, 2013
  7. Junio C HamanoFeb 22, 2013

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.