Re: Unmodified submodules shows up as dirty with 1.6.6.443.gd7346
- From
Jacob Helwig <jacob.helwig@gmail.com>
- Date
- Jan 18, 2010, 16:02 UTC
- Message-ID
- <8c9a061001180802t5ec0d389j2cae9f1771130c36@mail.gmail.com>
- In-Reply-To
- <4B547EA6.5070203@isy.liu.se>
On Mon, Jan 18, 2010 at 07:30, Gustaf Hendeby <hendeby@isy.liu.se> wrote:
Show 22 quoted lines
> Hi! > > I have been using submodules for a while, and been quite happy with > them. Just updating to the latest next (1.6.6.443.gd7346), a strange > problem has occurred. All my submodules (which are in fact unmodified) > show as modified and dirty > > diff --git a/extern/utils b/extern/utils > --- a/extern/utils > +++ b/extern/utils > @@ -1 +1 @@ > -Subproject commit 6bad20e1419f1ca61bd5a6eef9b5937122e006f1 > +Subproject commit 6bad20e1419f1ca61bd5a6eef9b5937122e006f1-dirty > > > Anyone have an idea what is going on here? (Related to the recent topic > by Jens Lehmann? cc:ed) Unfortunately, I don't have the time to dig > into this right now, but I'll try to do it later tonight if the problem > remains. > > /Gustaf >
Do you have any untracked files in the submodule? git status is working as I would expect with the same version (1.6.6.443.gd7346).
If there is no output from git status in the submodule, then git status in the superproject shows the submodule as being clean. However, if there is _any_ output from git status (untracked files, modified files, deleted files, new files), then the superproject shows the submodule as being dirty.
-Jacob