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

Integrity check

From
KJKenneth Johansson <ken@canit.se>
Date
Jun 6, 2006, 22:46 UTC
Message-ID
<pan.2006.06.06.22.46.26.518589@canit.se>

Iwas doing a git pull that ended badly and I thought that just redoing the command may help but then git thinks everything is just fine.

After a few failed attempts I still have not find a good way to make sure that everything is indeed correct. What is the suggested commands to do that ?

--------
Updating from 7705a8792b0fc82fd7d4dd923724606bbfd9fb20 to
1def630a6a49dda5bc89dfbd86656293640456f0 Checking files out...
 100% (6311/6311) done
Fast forward
*** glibc detected *** malloc(): memory corruption: 0x0a703e80 ***
/home/ken/bin/git-merge: line 56: 14121 Aborted                
git-diff-tree -p --stat --summary -M "$head" "$1" 
>git pull
* refs/heads/origin: same as branch 'master' of
/delta/kernel/git/linux-2.6/ Already up-to-date.
[
Next: Linus Torvalds
Message 1 of 4 in “Integrity check”
  1. Kenneth JohanssonJun 6, 2006
  2. Linus TorvaldsJun 6, 2006
  3. Linus TorvaldsJun 6, 2006
  4. Dave JonesJun 7, 2006

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.