3 ms·
>I do not think it is as black and white as you describe it. The way I see it: if somebody falsifies a complete repository No, it is. You can't "falsify a com
by danssig 15y ago
>I do not think it is as black and white as you describe it. The way I see it: if somebody falsifies a complete repository
No, it is. You can't "falsify a complete repository". We will all have checked out from that repo and as soon as someone replaces it with a fake none of the hashes will match up.
>the only way to detect that it was changed is by comparing its content or a hash thereof with that of a (supposed) copy that is more trusted.
Which happens in the system automatically. Have you actually worked with Git? Go change history on something you've pushed and other people have pulled.
>number of people keeping a copy who will not blindly copy changes from the 'main' repository.
It's not about "blindly copy changes". If you pull from a repo where someone has tried to rewrite history you'll see duplicate entries all over your log. If you have a graphical tool you'll see right where they started their modification.