git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kārlis Repsons" <karlis.repsons@gmail.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git@vger.kernel.org
Subject: Re: Repository authenticity question
Date: Wed, 17 Jun 2009 07:57:51 +0000	[thread overview]
Message-ID: <200906170757.59476.Karlis.Repsons@gmail.com> (raw)
In-Reply-To: <4A33C980.40003@drmicha.warpmail.net>

[-- Attachment #1: Type: text/plain, Size: 966 bytes --]

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?

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2009-06-17  7:58 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 [this message]
2009-06-17  8:07     ` Michael J Gruber

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=200906170757.59476.Karlis.Repsons@gmail.com \
    --to=karlis.repsons@gmail.com \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    /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).