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

Re: checking sha1's of files

From
Caleb Cushing <xenoterracide@gmail.com>
Date
Feb 8, 2009, 12:22 UTC
Message-ID
<81bfc67a0902080422s7f12d86ft5196c184c06385f9@mail.gmail.com>
In-Reply-To
<20090208111343.GC14359@coredump.intra.peff.net>
> So if I understand you correctly, you would use the former when
> generating your manifests from a revision, and the latter when verifying
> the contents of the filesystem against those manifests.

that sounds about right actually. except there won't be manifests e.g. I may actually run

find . -name Manifest -exec rm '{}' +

from the root of the tree. (depends on whether I can get rid of manifesting distfiles, but they don't change so often, so aren't really a problem).

>  $ git hash-object --stdin < Makefile
>  27b9569746179e68c635bdaab8e57395f63faf01

is there anyway built in way to do that and check to see if the hash matches HEAD? (before I go and write a string comparison so that it does)

-- 
Caleb Cushing

http://xenoterracide.blogspot.com
Previous: Jeff KingNext: Jeff King
Message 5 of 7 in “checking sha1's of files”
  1. Caleb CushingFeb 8, 2009
  2. Junio C HamanoFeb 8, 2009
  3. Caleb CushingFeb 8, 2009
  4. Jeff KingFeb 8, 2009
  5. Caleb CushingFeb 8, 2009
  6. Jeff KingFeb 8, 2009
  7. Caleb CushingFeb 8, 2009

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.