From: Junio C Hamano <gitster@pobox.com>
To: Caleb Cushing <xenoterracide@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: checking sha1's of files
Date: Sun, 08 Feb 2009 01:58:35 -0800 [thread overview]
Message-ID: <7veiy9z1v8.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <81bfc67a0902080139j1331d967g34bfc18f4068e443@mail.gmail.com> (Caleb Cushing's message of "Sun, 8 Feb 2009 04:39:19 -0500")
Caleb Cushing <xenoterracide@gmail.com> writes:
> I need to check the hashes of specific files in the repo in an
> automated fashion, in another tool.
What "hash" are you talking about? sha1? md5? crc?
I *think* you are trying to say that gentoo has a tool to compute some
sort of hash for regular files in their source tree by:
"gentoo's portage tree has manifests for each file"
but without knowing what kind of hash they use, I cannot tell you if you
can reuse some part of git to compute their hash without using their tools
(it also is unclear why you are not using their tool to compute their hash
and instead are expecting git to know about the specific hash function
used by them).
For exammple,
"sha1sum Makefile"
would give you the SHA-1 checksum of the contents of the Makefile. Is
that what gentoo's tools expect? If that is the case, that is different
from the blob object name git will give to the contents of that Makefile,
so you cannot reuse much of git.
next prev parent reply other threads:[~2009-02-08 10:00 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 [this message]
2009-02-08 10:53 ` Caleb Cushing
2009-02-08 11:13 ` Jeff King
2009-02-08 12:22 ` Caleb Cushing
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=7veiy9z1v8.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=xenoterracide@gmail.com \
/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).