From: Jonathan del Strother <maillist@steelskies.com>
Date: Sat, 30 Jan 2010 16:36:45 GMT
Subject: Re: v1.7.0-rc0 shows lots of "unable to find <sha1>" on git-stash
Message-ID: <57518fd11001300836v7f21a8a9qc09953d9091a4513@mail.gmail.com>
In-Reply-To: <4B643DEF.8010809@web.de>

On 30 January 2010 14:10, Jens Lehmann <Jens.Lehmann@web.de> wrote:
> Am 30.01.2010 14:23, schrieb Jonathan del Strother:
>> On 30 January 2010 12:31, Jens Lehmann <Jens.Lehmann@web.de> wrote:
>>> I assume you have one or more submodules, maybe even with untracked
>>> or yet uncommitted modified files in your tree? If so, what does git
>>> status say in the superproject and in the submodule(s)?
>>
>> Yep, I have 10 submodules.  However, they're all completely clean with
>> no tracked or untracked changes shown in git status.  Anything else I
>> can investigate?
>
> The change in behavior my patch introduced is that "git status" is
> called inside each submodule. So i would expect getting the same
> errors when using this command:
>   git submodule foreach git status -s
>
> It should just show
>   Entering '<submodule 1>'
>   Entering '<submodule 2>'
>   Entering '<submodule 3>'
>   Entering '<submodule 4>'
>   Entering '<submodule 5>'
>   Entering '<submodule 6>'
>   Entering '<submodule 7>'
>   Entering '<submodule 8>'
>   Entering '<submodule 9>'
>   Entering '<submodule 10>'
> when the submodules are not dirty. What do you get?
>

Correct - I just get that output.