Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: > On Tue, 5 Dec 2006, Junio C Hamano wrote: >... >> The current use of "git status" inside "git commit" needs to be revamped >> if we pursue this further, though. Because one of the points the "what >> state is this repository in" check "explain" does is to define what >> operations are sensible in each state, and most likely in many state it >> would not make _any_ sense to run "git commit" (say, in the middle of >> "bisect"). > > That is right, but it is only a matter of having a command line switch to > suppress what you do not need for the commit message. After all, "status" > really should tell you about the status of the working directory. The fact > that we have the _same_ script for "commit" and "status" is no excuse! Sure. The way I envisioned it was that we would have a moral equivalent of current git-status output for explanation of the base state. I originally wanted to do "git oops" which would have been a universal "undo" command, and "explain" was only the first smaller step toward that goal. But the more I think about it, I feel that "undo" is less important. - 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