Michael Witten <mfwitten@xxxxxxxxx> writes: >> Even if you use it normally: >> >> # I want to create a new root commit with a different tree >> git checkout -b new-project >> # hack for a while >> git status >> # ?!? why are files shown as 'deleted', 'moved', 'modified', I said I >> # was creating a new project! >> >> Also, with your proposal, we would need to add two flags to "commit" >> (--no-parent and --force), which is one of the first command beginners >> learn, while in the current state we have just one for "checkout" to do >> the trick, and newbies do not use or read the doc for checkout, so it's >> not scary for them. > > Well, those are mildly interesting scenarios. I can only say that I don't > think we should cater to people who either have amnesia or work casually > on a repository for short bursts every few months or so. How is the "git status" issue above linked to any kind of amnesia? When hacking to create a rootless commit, it seems legitimate to me to run "git status", and it seems _very_ confusing that "git status" still refers to the commit you don't want as parent. (I don't get the relation between your reply and the paragraph right above it either) -- Matthieu Moy http://www-verimag.imag.fr/~moy/ -- 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