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

Re: What's cooking in git.git (Apr 2017, #01; Tue, 11)

From
Christian Couder <christian.couder@gmail.com>
Date
Apr 11, 2017, 10:12 UTC
Message-ID
<CAP8UFD2PitxZDMm+qRrFOj+tQQsEUadOiQQjXjDnBCuHd9m21g@mail.gmail.com>
In-Reply-To
<xmqqh91vqquf.fsf@gitster.mtv.corp.google.com>
Show 8 quoted lines
> * cc/split-index-config (2017-03-30) 1 commit
>  - read-cache: avoid using git_path() in freshen_shared_index()
>
>  The split-index code configuration code used an unsafe git_path()
>  function without copying its result out.
>
>  Needs to be explained better.
>  The code looked OK, though.
In:
http://public-inbox.org/git/xmqq7f367o0s.fsf@gitster.mtv.corp.google.com/

it looked like you were ok with the explanation or you actually wanted it to be shorter. So should I send a shorter one? Or should I add explanation about why git_path() is unsafe?

Previous: Junio C HamanoNext: Jonathan Nieder
Message 2 of 4 in “What's cooking in git.git (Apr 2017, #01; Tue, 11)”
  1. Junio C HamanoApr 11, 2017
  2. Christian CouderApr 11, 2017
  3. Jonathan NiederApr 11, 2017
  4. Jeff KingApr 12, 2017

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.