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

Re: [PATCH] git-diff: don't squelch the new SHA1 in submodule diffs

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Sep 9, 2007, 00:18 UTC
Message-ID
<Pine.LNX.4.64.0709090117331.28586@racer.site>
In-Reply-To
<20070908103022.GA15229MdfPADPa@greensroom.kotnet.org>
Hi,
On Sat, 8 Sep 2007, Sven Verdoolaege wrote:
Show 7 quoted lines
> The code to squelch empty diffs introduced by commit
> fb13227e089f22dc31a3b1624559153821056848 would inadvertently
> populate filespec "two" of a submodule change using the uninitialized
> (null) SHA1, thereby replacing the submodule SHA1 by 0{40} in the output.
> 
> This change teaches diffcore_skip_stat_unmatch to handle
> submodule changes correctly.

Ah, I was wondering... This struck me as odd in msysGit, but I did not know if it was a problem I introduced in 4msysgit or not. Unfortunately, I did not have the time to investigate further.

Thanks, Dscho

Previous: Sven Verdoolaege
Message 2 of 2 in “git-diff: don't squelch the new SHA1 in submodule diffs”
  1. git-diff: don't squelch the new SHA1 in submodule diffsSven Verdoolaege, Sep 8, 2007
  2. Johannes SchindelinSep 9, 2007

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.