From: Michael J Gruber <git@drmicha.warpmail.net>
To: "Kārlis Repsons" <karlis.repsons@gmail.com>
Cc: Michael J Gruber <git@drmicha.warpmail.net>, git@vger.kernel.org
Subject: Re: Repository authenticity question
Date: Wed, 17 Jun 2009 10:07:56 +0200 [thread overview]
Message-ID: <4A38A45C.6080708@drmicha.warpmail.net> (raw)
In-Reply-To: <200906170757.59476.Karlis.Repsons@gmail.com>
Kārlis Repsons venit, vidit, dixit 17.06.2009 09:57:
> On Saturday 13 June 2009 15:45:04 you wrote:
>> Kārlis Repsons venit, vidit, dixit 13.06.2009 17:26:
>>> Hi,
>>> It would be good to know what did Linus meant, when he said "and they
>>> will fail" about people, who would try changing some git projects'
>>> history (that is, the content, that is added already)? If I loose my
>>> repository completely, can I still know, that those contributions there
>>> are the same after I pull and how? What contents can be deleted, while
>>> still retaining consistency?
>>>
>>> Regards,
>>> Kārlis
>>
>> The sha1 ("object name") of a commit depends not only on its contents,
>> but on all its predecessors. So if you know one commit's sha1 to be
>> "original" you know for all its ancestors.
>>
>> Michael
>
> So, if I clone someone else's git archive, sha1 of a known commit must be
> compared and what else? How to check if all of archive's sha1-s are identical
> to its contents and every content is included?
As I said: if the sha1 of one commit agrees with what what you have or
know then, automatically, all ancestry is "original": commits as well as
contents.
You can check the repo itself using "git fsck", this makes sure that all
referenced content is included.
Michael
prev parent reply other threads:[~2009-06-17 8:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-13 15:26 Repository authenticity question Kārlis Repsons
2009-06-13 15:45 ` Michael J Gruber
2009-06-17 7:57 ` Kārlis Repsons
2009-06-17 8:07 ` Michael J Gruber [this message]
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=4A38A45C.6080708@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=karlis.repsons@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).