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

Re: [PATCH v2] reftable/writer: ensure valid range for log's update_index

From
Toon Claes <toon@iotcl.com>
Date
Dec 11, 2024, 13:10 UTC
Message-ID
<871pyejrfi.fsf@iotcl.com>
In-Reply-To
<CAOLa=ZRYDqhAPMiuAS-HGaC1huiUGgLW3hL_dDNwrFA5c8ewEQ@mail.gmail.com>
karthik nayak <karthik.188@gmail.com> writes:
> I was reading the reftable code and noticed it. So mostly luck. Agreed
> with what you're saying, I'd say this is mostly a 'safeguard'.
I was wondering as well, thanks for that info.
> Totally, these kind of specific changes are perfect for unit-tests. Plus
> it was very simple to add one too.

I appreciate you're doing this, that makes it easier to reason about these changes.

>> Will queue.  Thanks.

Junio, thank you for the quick turnarond on this patch. For what it's worth, I've given this a review and I approve these changes.

-- 
Toon
Previous: karthik nayak
Message 7 of 7 in “reftable/writer: ensure valid range for log's update_index”
  1. reftable/writer: ensure valid range for log's update_indexKarthik Nayak, Dec 5, 2024
  2. Patrick SteinhardtDec 6, 2024
  3. karthik nayakDec 6, 2024
  4. reftable/writer: ensure valid range for log's update_indexKarthik Nayak, Dec 6, 2024
  5. Junio C HamanoDec 6, 2024
  6. karthik nayakDec 7, 2024
  7. Toon ClaesDec 11, 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.