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

Re: [GSoC][RFC] discussion about stashing with conflicts

From
KJKapil Jain <jkapil.cs@gmail.com>
Date
Apr 8, 2019, 14:27 UTC
Message-ID
<CAMknYENGZBQ6-8sJ5UrKS_ZLLoz79K8FYUHFQqSpV2JrkSuf6w@mail.gmail.com>
In-Reply-To
<CACsJy8D7mQZgJhZ4H8Z929EnjYe1Wp7idrbXqkUsmL1Ypn83dg@mail.gmail.com>

while understanding add_index_entry_with_check() i got to do_invalidate_path().

the commit hash for do_invalidate_path() function is `749864627c2d3c33bbc56d7ba0b5542af698cc40`

in the commit message it is explained that, cache-tree is used to store object names of index file objects and it is kept separate from index file because adding it would change index file format.

the part i couldn't understand is: "During various index manupulations, we selectively invalidate the parts so that the next write-tree can bypass regenerating tree objects for unchanged parts of the directory hierarchy."

what exactly does invalidating means here ?
Previous: Duy NguyenNext: Thomas Gummerer
Message 7 of 8 in “[GSoC][RFC] discussion about stashing with conflicts”
  1. Kapil JainApr 7, 2019
  2. Thomas GummererApr 7, 2019
  3. Kapil JainApr 8, 2019
  4. Duy NguyenApr 8, 2019
  5. Kapil JainApr 8, 2019
  6. Duy NguyenApr 8, 2019
  7. Kapil JainApr 8, 2019
  8. Thomas GummererApr 8, 2019

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.