A tracking tree for the active work space

["Jon Smirl" <jonsmirl@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