git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Caleb Cushing <xenoterracide@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: checking sha1's of files
Date: Sun, 8 Feb 2009 07:22:31 -0500	[thread overview]
Message-ID: <81bfc67a0902080422s7f12d86ft5196c184c06385f9@mail.gmail.com> (raw)
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

  reply	other threads:[~2009-02-08 12:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-08  9:39 checking sha1's of files Caleb Cushing
2009-02-08  9:58 ` Junio C Hamano
2009-02-08 10:53   ` Caleb Cushing
2009-02-08 11:13     ` Jeff King
2009-02-08 12:22       ` Caleb Cushing [this message]
2009-02-08 12:27         ` Jeff King
2009-02-08 12:57           ` Caleb Cushing

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=81bfc67a0902080422s7f12d86ft5196c184c06385f9@mail.gmail.com \
    --to=xenoterracide@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).