A Large Angry SCM wrote:
>Stephen R. van den Berg wrote:
>>No it does not.
>>The cryptographic seal is calculated over the content of the commit,
>>which includes the hashes of all referenced objects, but doesn't include
>>the objects themselves.
>>The content of the commit is not violated.
>The fetch MUST gather the referenced objects ALWAYS or I can't verify
>the history. To do otherwise means that ID strings on the origin lines
>are nothing more than an arbitrary text tag and not pointer to a
>specific history.
To fetch, by default, the origin lines *are* nothing more than arbitrary
text and not a pointer to a specific history.
>How do I verify (think git-fsck) that what the origin lines refer to
>are, in fact, commits with the proper relationships? Either they HAVE to
>be in the repository or the references do not belong in the header.
If the origin hashes are not reachable, then fsck is required to silently
skip them, according to spec.
If the origin hashes *are* reachable, then fsck is required to verify
that they refer to proper commits with a normal history.
--
Sincerely,
Stephen R. van den Berg.
"There are three types of people in the world;
those who can count, and those who can't."
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
