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

A tracking tree for the active work space

From
Jon Smirl <jonsmirl@gmail.com>
Date
Mar 11, 2007, 14:06 UTC
Message-ID
<9e4733910703110706m14abae25r2a965b644d8c3bbb@mail.gmail.com>

Reading the other thread on tracking temporary changes made me think of using inotify with git. The basic idea would be to a daemon running that uses inotify to listen for changes in the working tree. As these changes happen they get committed to a tracking tree.

The tracking tree serves two purposes. First it is a good way to recover from programmer error. I have definitely written big chunks of code, discarded them, and then realized later that they were the right solution and had to write them again.

The tracking tree also makes a 'git grep' for uncommitted changes easier to implement since the changes are always committed with this model. For dual processors the inverted index can be computed in parallel with editing.

Of course this daemon needs some smarts. You don't want it generating a delta the hard way from a git check out of a different workspace It will also make real check-ins instant since you just copy the tip of the tacking tree.

-- 
Jon Smirl
jonsmirl@gmail.com
Next: Junio C Hamano
Message 1 of 7 in “A tracking tree for the active work space”
  1. Jon SmirlMar 11, 2007
  2. Junio C HamanoMar 11, 2007
  3. Jon SmirlMar 11, 2007
  4. Johannes SchindelinMar 11, 2007
  5. Jeff KingMar 11, 2007
  6. Jon SmirlMar 12, 2007
  7. Johannes SchindelinMar 11, 2007

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.