Thread (6 messages) flat view 6 messages, 2 authors, 2016-06-15

Re: v1.7.0-rc0 shows lots of "unable to find <sha1>" on git-stash

From: Jonathan del Strother <hidden>
Date: 2016-06-15 22:48:08

Possibly related (same subject, not in this thread)

On 30 January 2010 14:10, Jens Lehmann [off-list ref] wrote:
Am 30.01.2010 14:23, schrieb Jonathan del Strother:
quoted
On 30 January 2010 12:31, Jens Lehmann [off-list ref] wrote:
quoted
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.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help