Scott Chacon <schacon@xxxxxxxxx> writes: > For example, implementation details aside, I think having something > like WTREE and NEXT available would help users understand that there > are these 3 trees that are important and useful in Git and re-inforce > a very non-SVN style workflow in that manner. That's a funny thing to say. Working tree may almost always (to put it another way, "you could make it to") act like a tree, but the index does not act like a tree at all in more important situations. For example, how would you design the user experience of "git show NEXT"? Try to write a transcript (i.e. "The user starts from this state, runs these commands, and then says 'git show NEXT'. The user will see this."), covering various corner cases exhaustively, including what would happen before the first commit, and during a conflicted "pull" or "rebase -i". It's not just the matter of "internally pretend to run write-tree with 'not committed yet' as a fake commit log message and show it as if it is an existing commit. I wouldn't demand "implement 'git show NEXT'" here, nor "implement it efficiently" here; just designing the user experience is a good first step to realize that the index does not act like a tree, and I do not think you should spread such a misconception to the end users. -- 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