3 ms·
Consider the bit at the end of this blog post: https://devblogs.microsoft.com/oldnewthing/20180326-00/?p=98335 https://devblogs.microsoft.com/oldnewthing/20180
by rcxdude 6y ago
Consider the bit at the end of this blog post:
https://devblogs.microsoft.com/oldnewthing/20180326-00/?p=98335 https://devblogs.microsoft.com/oldnewthing/20180326-00/?p=98...
Bonus chatter: In a discussion of Windows source control, one person argued that git works great on large projects and gave an example of a large git repo: “For example, the linux kernel repository at roughly eight years old is 800–900MB in size, has about 45,000 files, and is considered to have heavy churn, with 400,000 commits.”
I found that adorable. You have 45,000 files. Yeah, call me when your repo starts to get big. The Windows repo has over three million files.
Four hundred thousand commits over eight years averages to around [130] commits per day. This is heavy churn? That’s so cute.
You know what we call a day with [130] commits? “Catastrophic network outage.”
- jka 6y agoTo get closer to an apples-to-apples comparison, it'd be necessary to know whether the commit counts in each case include all development branches for all development groups. By design, git-based development can be highly distributed. Also, even if we normalized both cases for 'code files only' and/or 'kernel code only', there could still be architectural, code style, and development process differences that lead to different metrics for each project.
- deleted 6y ago[deleted]
- AlexCoventry 6y agoHe's really not selling Microsoft as a fun place to work, is he?