David Jeske wrote: >> -- David Jeske wrote: >>> - improve the man page description of "reset --hard" >>> - standardize all the potentially destructive operations >>> (after gc) on "-f/--force" to override >> The thing is 'force' is not always the most descriptive word >> for the behavior that you propose enabling with --force. > I'm not talking about switching "git reset --hard" to "git reset -f". I'm > talking about requiring a "-f" option to "git reset --hard" when it would > destroy or dangle information. I only have the same advice I gave to Boaz. I think you should try to adjust your workflow so that 'git reset' is not necessary. It seems that for the functions you're trying to perform, 'checkout' and 'branch' should be used rather than 'reset'. Again, as I mentioned to Boaz, there is really no benefit to reusing a single branch name if that is what you are trying to do. The cost of branching in git is 41 bytes i.e. nil. The cost of updating the working directory which happens during the 'reset --hard' is exactly the same whether I do 'reset --hard <some_branch>' or 'checkout -b new_branch <some_branch>'. In nearly every case where I, personally, have used 'reset --hard', I was using it because I didn't care what the current state of the working directory or the index were. They were wrong and I was resetting to the right state. I believe this was the intended use for the command. I'm not sure why you want to use reset so often. If there is something in the documentation that led you to want to use reset maybe it can be changed so that other users are not led in the same way. About the reflog.. The reflog is not a storage area. It's just a log, like /var/log/messages. It is there to provide a way to recover from mistakes. Mistakes are usually recognized fairly quickly. If you have not realized that you have made a mistake after 30 days, it may be pretty hard to recover from since people have imperfect memories. If we did not garbage collect the reflog it would just continue to grow appending useless piece of information after useless piece of information. -brandon -- 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
