git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Jonathan del Strother <maillist@steelskies.com>
Date
Jan 30, 2010, 13:23 UTC
Message-ID
<57518fd11001300523xf7d931by254581c8494171af@mail.gmail.com>
In-Reply-To
<4B642696.2070501@web.de>
On 30 January 2010 12:31, Jens Lehmann <Jens.Lehmann@web.de> wrote:
Show 23 quoted lines
> Am 30.01.2010 01:46, schrieb Jonathan del Strother:
>> On 29 January 2010 17:44, Junio C Hamano <gitster@pobox.com> wrote:
>>> Jonathan del Strother <maillist@steelskies.com> writes:
>>>
>>>> Heya,
>>>>
>>>> git-stash in v1.7.0-rc0 gives me several hundred lines of :
>>>> The previous build I was using -
>>>> 5b15950ac414a8a2d4f5eb480712abcc9fe176d2 from Jan 19th - didn't show
>>>> this problem.  Want me to try and bisect further?
>>>
>>> Yes, please.
>>>
>>
>> ee6fc514f2df821c2719cc49499a56ef2fb136b0 (Show submodules as modified
>> when they contain a dirty work tree) seems to be the first bad commit.
>
> Thanks for pinning that down.
>
> 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?

Previous: Jens LehmannNext: Jens Lehmann
Message 4 of 13 in “v1.7.0-rc0 shows lots of "unable to find <sha1>" on git-stash”
  1. Jonathan del StrotherJan 29, 2010
  2. Jonathan del StrotherJan 30, 2010
  3. Jens LehmannJan 30, 2010
  4. Jonathan del StrotherJan 30, 2010
  5. Jens LehmannJan 30, 2010
  6. Jonathan del StrotherJan 30, 2010
  7. Junio C HamanoJan 30, 2010
  8. Junio C HamanoJan 30, 2010
  9. is_submodule_modified(): fix breakage with external GIT_INDEX_FILEJunio C Hamano, Jan 30, 2010
  10. Jonathan del StrotherJan 31, 2010
  11. Jonathan del StrotherJan 31, 2010
  12. Junio C HamanoJan 31, 2010
  13. Jens LehmannJan 30, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.