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

Re: git-write-tree strangeness

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 8, 2007, 19:39 UTC
Message-ID
<7vabt14y08.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<81b0412b0708080910u3aee166fo92ea73a4a0a78ccf@mail.gmail.com>
"Alex Riesen" <raa.lkml@gmail.com> writes:
Show 11 quoted lines
> On 8/8/07, Steven Walter <stevenrwalter@gmail.com> wrote:
>> I'm importing a large repository from svn into git with a custom tool,
>> and I noticed a strange issue with one of the commits.
>>
>> Upon investigating further, I found that when I ran "git-write-tree"
>> followed immediately by "git-diff-index <tree>" I had differences.  Does
>> that mean that git-write-tree incorrectly recorded the index, or do I
>> misunderstand things?
>
> What kind of differences? Different sha1 of content?
> I can't simply reproduce it.

Isn't this simply just a dirty worktree and missing --cached option?

Previous: Alex RiesenNext: Steven Walter
Message 3 of 4 in “git-write-tree strangeness”
  1. Steven WalterAug 8, 2007
  2. Alex RiesenAug 8, 2007
  3. Junio C HamanoAug 8, 2007
  4. Steven WalterAug 8, 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.