Re: regression in git-gui since 2c5c66b... Merge branch 'jp/get-ref-dir-unsorted
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Oct 17, 2011, 00:35 UTC
- Message-ID
- <7vfwispi8u.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <4E9B1E32.7030101@gmail.com>
Mark Levedahl <mlevedahl@gmail.com> writes:
Show 7 quoted lines
> 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.