Re: .git/binary

From: Philip Oakley <philipoakley@iee.email>
Date: Oct 25, 2019, 20:59 UTC
Message-ID: <5f558e34-bdb2-6656-d2ca-42a2d7cb8874@iee.email>
In-Reply-To: <24796381572021130@iva7-56e9317134d0.qloud-c.yandex.net>

On 25/10/2019 17:32, без имени wrote:

>> Or were you thinking of some other meaning for "files stored in a single (current) state"?
> It means that new versions of files located in `.git / binary` will completely replace old versions in history, and therefore will be in a single (current) state in history. What used to be another version of this file should be ignored (very useful for PNG, JPEG, PDF).
>

"completely replace old versions in history" : but why?
- Is it a space (size on disc, or memory) problem/limitation
- A confidentiality problem?
- A 'must use latest procedure' (always checkout latest instructions) 
problem?
- A synchronisation problem (no adequate diff) needing single line of 
development? (there was a discussion at Git Merge in February about this 
for modified Audio-Visual (AV) files in Games development

“Git for games: current problems and solutions” presentation by John
Austin at Git Merge 2019:
   https://www.youtube.com/watch?v=K3zOhU3NdWA&list=PL0lo9MOBetEFqBue4vNcTEnkBjgIQU1Q3&index=8&t=0s

- Something else?

The main advantage of Git is that it distributes control from some central 'manager' to the individual and does that by taking snapshots and exchanging verification stamps, so the idea of deleting history feels somehow 'wrong', hence the need to understand

-- 
Philip