Programming

17444 readers

147 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

Highlights from git 2.42 (github.blog)

submitted 1 year ago* (last edited 1 year ago) by starman@programming.dev to c/programming@programming.dev

16 comments fedilink hide all child comments

Full release notes

you are viewing a single comment's thread
view the rest of the comments

[–] severien@lemmy.world 2 points 1 year ago (1 children)

The obvious choice would’ve been to not use it and state the numbers plainly.

How would you write it?

[+] Illecors@lemmy.cafe -9 points 1 year ago (1 children)

The open source Git project just released Git 2.42 with features and bug fixes from 78 contributors, 17 of them new.

There. Simple.

[–] severien@lemmy.world 6 points 1 year ago* (last edited 1 year ago) (1 children)

But there were more contributors, you just don't know how many. By this you're kind of disregarding their work.

[+] Illecors@lemmy.cafe -10 points 1 year ago (1 children)

No there aren't, stop making things up. From the official release notes:

The latest feature release Git v2.42.0 is now available at the
usual places.  It is comprised of 453 non-merge commits since
v2.41.0, contributed by 78 people, 17 of which are new faces

[–] severien@lemmy.world 4 points 1 year ago* (last edited 1 year ago) (1 children)

78 people contributed in the form of code commits, but more people likely contributed to the release in other ways (QA, triage, release management etc.)