Comment on Git 2.42
severien@lemmy.world 1 year agoMaybe there were 78 committers. But other people contributed to the release in some other way (QA?), but that may be more difficult to count than just looking at the commit stats …
Comment on Git 2.42
severien@lemmy.world 1 year agoMaybe there were 78 committers. But other people contributed to the release in some other way (QA?), but that may be more difficult to count than just looking at the commit stats …
Illecors@lemmy.cafe 1 year ago
Sorry, I failed to relay my point. When somebody writes over x amount - it’s always a rounded number. This smells of either pre-highschool levels of language or some ML generated content.
severien@lemmy.world 1 year ago
The author of the blogpost is a developer, not a professional writer. Honestly I don’t understand why you’re so upset about it.
Illecors@lemmy.cafe 1 year ago
I’m upset about it because it lacks attention to detail. Language is tricky, but this is an attempt to use an expression without understanding what it is. The obvious choice would’ve been to not use it and state the numbers plainly.
Tamo@programming.dev 1 year ago
Perhaps the numbers are not plainly available as the previous commenter stated, and they wanted to call out the direct contribution of the 78 unique commit authors, without disregarding many other indirect contributions from commenters, reviewers, testers etc.
Marzepansion@programming.dev 1 year ago
It’s perhaps better that patch notes are written by programmers and not linguists. Incorrectly using a (harmless) phrase is perfectly okay. It doesn’t detract from the important bits of the announcement at all.
severien@lemmy.world 1 year ago
How would you write it?
Sibbo@sopuli.xyz 1 year ago
Usually, also people who write in issues or discuss things are counted as contributors, but there it is pretty hard to figure out who contributed to this specific release