this post was submitted on 11 Jan 2025
81 points (98.8% liked)

Linux

5594 readers
232 users here now

A community for everything relating to the linux operating system

Also check out !linux_memes@programming.dev

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago
MODERATORS
Ategon@programming.dev
anzo@programming.dev
dwraf_of_ignorance@programming.dev
81
Git 2.48 released (github.blog)
submitted 1 day ago by petsoi@discuss.tchncs.de to c/linux@programming.dev
12 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] Phen@lemmy.eco.br 9 points 1 day ago (4 children)

Wait, git evolves?

[–] FizzyOrange@programming.dev 14 points 1 day ago

Yep, whenever they fix a bug it's added in a new flag that nobody knows about.

git --enable-sane-behaviour
[–] kbal@fedia.io 3 points 1 day ago (1 children)

As a casual git user I imagine the process normally goes something like this:

  1. Development happens.
  2. New feature makes it into the release version of git.
  3. New version makes it into the various linux distro repositories.
  4. People who run big git repos install the update.
  5. Serious nerds hear about it and use the feature.
  6. Many years pass.
  7. I learn about it, if it's widely used enough.
[–] colorado@programming.dev 1 points 13 hours ago (1 children)

The big change in my opinion is we don't need to tell newcomers about git checkout at all. Git switch --create is much better.

[–] timbuck2themoon@sh.itjust.works 2 points 12 hours ago

I'm so old I still just use git checkout -b somebranch anyway.

[–] Mauryamj@programming.dev 1 points 1 day ago

U are the only one who knows my pain