Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: >> That's exactly the point. The option reads "ignore submodules", not >> "special option for use only by stash and rebase". > > But it also does not read "ignore submodules and those blobs/trees that > happen to replace (or be replaced by) submodules". I think "ignore submodules" option, if exists, would mean "ignore changes that involve submodules", and I think everybody would agree with that. Because we are talking about an option to "diff", changes involve two sides (preimage and postimage). Logically, you can define the class of changes that involve submodules in two ways: * both sides of the change must be a submodule; otherwise the change does not involve a submodule. * either side of the change is a submodule; such a change involve a submodule. I am saying that the latter makes much more sense (worse yet, what you did for creation and deletion is inconsistent --- they are void vs submodule and you treat them as "change that involve submodule"). Didn't you make the option introduction to read "sometimes you are not interested in submodules..." or something? -- 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
