Michael Witten wrote: > Commands like "git checkout" and "git reset" essentially operate on 2 > aspects of a repository: > > (1) The repository's state. > (2) The repository's working tree. > > Is there any reason why these commands can't just operate on (1) in a > bare repository, thereby allowing users to use familiar commands to > get their work done? Not that I can think of. I’d say go for it. (I’ll be glad to help in any way I can. Not sure I’ll have much time soon, but I can answer questions, look over patches, and so on.) > The "git checkout" command in a bare repository should serve to select > on which branch other commands (like "git reset") operate, etc. My only worry would be low-level scripts that want to be able to use a separate index or work tree with a bare repository. Maybe the index file could be in a special "bare" state to request the semantics you’re describing. Jonathan -- 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