If it doesn't fit anywhere else, drop it in here. (not to be used as a chat/nonsense section)
Moderator: Moderator Team
4 posts • Page 1 of 1
The spike down to 0 is at 2010-6-20, which is a parsing error due to the fact that that entry doesn't have an "M" following the size value for some reason. Thanks for making me take a second look!
The spike up to 69 happens at 2011-10-3 and 2011-10-4, starting at r53981 and ending at r53990 inclusive. Looking at the commit, I don't see anything obvious as to why this happened: https://github.com/reactos/reactos/comm ... 975b437d70
And no, I didn't separate GCC from MSVC - the noise at the end of the graph starts at 2017-10-03, when the first MSVC builds show up. The lower bounds of that noise are the MSVC builds, the upper bounds are the GCC builds.
Nice! My approach was much more of a 5 minute hack to make a quick chart. As you can see from my script: https://pastebin.com/wfvy8gD5 I used a local copy of the ISO page's HTML.ThFabba wrote: ↑Wed Jan 16, 2019 8:50 pmHey, I did that too...
https://gist.github.com/ThFabba/592205b ... b61f3610e1
Unfortunately I never updated it to support git... or Python 3.
Users browsing this forum: DotBot [Crawler] and 2 guests