Re: [PATCH 13/22] sequencer: remember the onelines when parsing the todo file

From: Junio C Hamano <gitster@pobox.com>
Date: Sep 1, 2016, 22:59 UTC
Message-ID: <xmqqvayftefc.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <63004be3-04de-00c5-a94d-1b600201bc6f@gmail.com>

Jakub Narębski <jnareb@gmail.com> writes:

> I wonder how probable is situation where we save instruction sheet
> for interactive rebase, with shortened SHA-1, and during rebase
> shortened SHA-1 stops being unambiguous...

It is my understanding that the shortened ones are only for end-user consumption. The insn sheet internally uses fully expanded form for this exact reason, and then abbreviated back at each step before the updated one is presented to the end-user. Uniqueness guarantee is enforced with new objects created during each step taken into account by doing it this way.

$ 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.