Mark Levedahl <mlevedahl@xxxxxxxxx> writes: > I have a project organized as a number of nested git modules (not > using git-submodule), and frequently use git-new-workdir to create the > nested modules. > > Since the above merge-commit, git-gui is confused by this arrangement > and reports every file in every nested module as being an untracked > file in the top-level (super) project. Could you come up with a simple reproduction recipe that prepares a superproject that has no file of its own, a submodule with a single file tracked, and attaches another workdir? If running git-gui in the resulting directory makes it misbehave, we could then isolate what git command that is invoked by git-gui has changed its behaviour. Thanks. -- 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