Andy Parkins <andyparkins@xxxxxxxxx> writes: > One additional small point: why do untracked files in a submodule make the > module dirty? I've often got a few "temp.ps" or "debug.log" or > "backtrace.log" files lying around -- inappropriate to add to an ignore > file, but they don't make my working directory dirty. "They don't make my working directory dirty" is something only you can decide, until you tell git about that fact, isn't it? The way to tell git about them is to use the ignore/exclude mechanism. Why are they "inappropriate to add to an ignore file"? At least you could have "*.log" in your personal exclude $GIT_DIR/info/exclude, no? As to the not-working-configuration I don't remember the codepath well, so sorry but no answer from me right now. -- 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