Re: [coreboot] [RFC] board-status.git growth

2016-02-18 Thread Timothy Pearson
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/17/2016 04:28 PM, Martin Roth wrote: > It's definitely an issue, and it's actually something that is > currently being looked into. As always, we just need someone to do > the work. :) > > There's a project listed on the project ideas wiki pag

Re: [coreboot] [RFC] board-status.git growth

2016-02-17 Thread Martin Roth
It's definitely an issue, and it's actually something that is currently being looked into. As always, we just need someone to do the work. :) There's a project listed on the project ideas wiki page about this, so maybe we'll get an enterprising person to work on it. If not, we'll probably conti

Re: [coreboot] [RFC] board-status.git growth

2016-02-17 Thread Patrick Georgi via coreboot
Hi Carl-Daniel, since last week I've started shopping around for options with people who know a thing or two when it comes to storing and processing large amounts of data. For the problem of submitters having to download the repo, I was thinking about setting up a relatively simple web service fr

Re: [coreboot] [RFC] board-status.git growth

2016-02-17 Thread Alex G.
Maybe using git a monotonically increasing entry count is the wrong way to go about it. That's beyond the scope, mission, design and goal of git. I would rethink the entire board-status mechanism to something more suited to the task than git. Yours truly, The Devil On 02/17/2016 01:07 PM, Carl-D

[coreboot] [RFC] board-status.git growth

2016-02-17 Thread Carl-Daniel Hailfinger
Hi, since various automated systems started submitting board status files, the board-status repository has grown significantly to a point where submitting a new board from scratch requires a download which is bigger than the whole coreboot repository. Once I hook up four more systems in my lab, I