kicad-developers team mailing list archive

[Tiger12506 <tiger12506@xxxxxxxxx>]

I have no authority in what happens, nor should you necessary take my 
advice, of course, but it might be wise to carefully consider how you 
want to store large binary data in git.

If the diffs do not make sense, and are large, then you are using 
version control about as inefficiently as you possibly can, and your 
fetch (part of pull) operation is going to get huge, fast.

One of the solutions for this (one at random that comes to mind, not 
endorsing it) is git-annex.

The time to think about this, IMHO, is before you create the repo.

On 3/10/2016 6:10 PM, Cirilo Bernardo wrote:
> I suggested splitting the 3D models long ago but there was some 
> resistance even though
> I really can't imagine how 3D models belong in a directory structure 
> with schematic symbols.
>
> Some thought would need to go into the organization of the 
> repositories and how these
> would look like as an offline directory structure for users who prefer 
> to pull the repositories.
> I think any STEP and IGES files should be compressed; their data 
> structure results in very
> high compression (often as much as 10:1). Although this would result 
> in crazy diffs, git
> will not complain. Crazy diffs on modifying STEP or IGES files is 
> inevitable anyway.
>
> I think ultimately a hosted solution with features similar to Altium's 
> "vault" is the way to
> go; however that requires some hosting infrastructure and development 
> of the API and
> any code/scripts to make it all happen.
>
> - Cirilo