I was toying around with the idea of keeping track of scripts or config files in my home directory. Most of the time my commits would include a change to the file I was tracking. However, there are a couple of cases where I wanted to commit empty diffs. For example, ideas or todos about that particular file that I didn't want to embed in the file itself nor write it in yet another file labeled ideas or todos. I thought it would be easier to just to run a 'git log' on the file and see my whole thought process. Considering git-commit doesn't allow this (probably for good reason), is it technically safe to do the following sequence of events? tree=$(git-write-tree) #basically the same tree HEAD points to commit=$(echo $IDEAS | git-commit-tree $tree -p HEAD) git-update-ref HEAD $commit HEAD I figured all a commit is doing is taking a snapshot of a particular tree at a moment in time. And taking multiple snapshots at that same moment and stringing them together (pointed to by HEAD) wouldn't be a big deal. Am I going to wind up shooting myself in the foot later or will this work? Light testing didn't show any issues. Thought I would ask the experts. Thanks. Cheers, Don - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html