Hi Nathan, On Tue, Aug 23, 2011 at 02:26:48PM -0500, Nathan W. Panike wrote: > > Is there any way to change this behavior, e.g., so that rule 6 becomes > an error? Say, by setting a config option? I know you're trying to improve git. I do not want to discourage that. But with little UI annoyances like this, it's usually not worth it. Git has countless magic tricks like this. It's a bit like perl in that regard. Assuming that we agree on what we would like to get rid of (which is the hard part), it would still break backwards compatibility. Maintaining a switch, on the other hand, is overhead and in the end it would make git even more complicated, because now the behavior of core commands depends on user configuration. But once you accept the fact that this is what git is, you can tackle the problem in a different way: > A colleague at $dayjob recently caused corruption in our git > repository by accidentally running the command > > git rebase origin stable Ok, mistakes happen. But that's exactly why you have git: To be able to deal with mistakes gracefully. So use git to review and test changes before they get declared as a stable release (stable enough to be used internally, at least). Then mistakes usually become a local problem and can be undone using the reflog. Clemens -- 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