Am 13.03.2010 23:24, schrieb Junio C Hamano: > Jens Lehmann <Jens.Lehmann@xxxxxx> writes: > >> Since 1.7.0 submodules are considered dirty when they contain untracked >> files. But when git status is called with the "-uno" option, the user >> asked to ignore untracked files, so they must be ignored in submodules >> too. To achieve this, the new flag DIFF_OPT_IGNORE_UNTRACKED_IN_SUBMODULES >> is introduced. >> >> Signed-off-by: Jens Lehmann <Jens.Lehmann@xxxxxx> >> --- >> >> This patch applies on top of current pu. >> >> I'm open to suggestions for a shorter name for the new diff option >> IGNORE_UNTRACKED_IN_SUBMODULES; I did not manage to come up with a >> shorter yet still descriptive enough name. > > Why do you even need that flag? Isn't it the matter of deciding to ignore > or pay attention to the DIRTY_SUBMODULE_UNTRACKED bit in the return value > of is_submodule_modified(), depending on whether the toplevel wt_status > was called with -uno? First: When called from "git status" run_diff_files() calls wt_status_collect_changed_cb() for every file it considers changed, so when the "-uno" option is given for a submodule with only untracked files i thought it cleaner to let is_submodule_modified() return 0 so this callback is not called at all and the submodule won't show up in the "change" list of wt_status (Yes, this could be done by not adding such a submodule to that list in the wt_status_collect_changed_cb() too). Second: One of my next patches will be about adding an option to the git diff family to not show submodules with only untracked files in their work tree as modified, which calls for such a diff option AFAICS. Third: We give is_submodule_modified() the possibility to stop parsing the output of the "git status" run in the submodule early, because as soon as it sees a modified file it will stop to parse the output further when untracked files shall be ignored. -- 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