Re: git-write-tree strangeness

"Alex Riesen" [off-list ref] writes:

On 8/8/07, Steven Walter [off-list ref] wrote:

quoted

I'm importing a large repository from svn into git with a custom tool,
and I noticed a strange issue with one of the commits.

Upon investigating further, I found that when I ran "git-write-tree"
followed immediately by "git-diff-index <tree>" I had differences.  Does
that mean that git-write-tree incorrectly recorded the index, or do I
misunderstand things?

What kind of differences? Different sha1 of content?
I can't simply reproduce it.

Isn't this simply just a dirty worktree and missing --cached
option?