kicad-developers team mailing list archive

[Marco Hess <marco.hess@xxxxxxxxxxxxxx>]

Just my 2c worth but that 'huge history' problem can be solved with 
using the
"shallow clone" capability of git.

i.e. git clone --depth 1 <cloneurl>

Also, I think that all the individual repositories could be combined
as sub modules of a larger master repository and then you just clone
a single repository and do an update sub modules?

Having said that, I don't use the github repositories other than an 
occasional
look as a reference when I am making a new part for my own libraries.

I keep my own libraries as a git repository on a shared drive. Git gives 
me the
ability to track changes (I particularly like the KiCad text based file 
formats for
this) and also a clone capability to move a library copy for offline use 
on laptops
Otherwise, the machines in my office simply use the shared drive.

Marco

On 18-Aug-15 07:55, Mark Roszko wrote:
> The github API is used to get the list of all repositories on the
> KiCad group on github. git alone cannot do that.
>
> However the zips from github are requested instead of checking out the
> repo via cloning. Theres definitely arguments for cloning vs not. One
> of the annoyances I see is some repos can have huge histories and you
> would stick a user would checking out that entire history the first
> time for multiple repos. That and dealing with force pushed masters
> and other messes.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

--
Marco Hess
Through IP Pty. Ltd. - AUSTRALIA
www.through-ip.com  | marco.hess@xxxxxxxxxxxxxx
p: +61 407 78 55 66 | f: +61 8 8121 6191