petsoi@discuss.tchncs.de to Linux@programming.dev · 20 days agoGit 2.48 releasedgithub.blogexternal-linkmessage-square11fedilinkarrow-up11arrow-down10
arrow-up11arrow-down1external-linkGit 2.48 releasedgithub.blogpetsoi@discuss.tchncs.de to Linux@programming.dev · 20 days agomessage-square11fedilink
minus-squarefoenkyfjutschah@programming.devlinkfedilinkarrow-up0·20 days agoit’s not recommended to boast about your ignorance.
minus-squareFizzyOrange@programming.devlinkfedilinkarrow-up0·20 days agoYep, whenever they fix a bug it’s added in a new flag that nobody knows about. git --enable-sane-behaviour
minus-squarekbal@fedia.iolinkfedilinkarrow-up0·20 days agoAs a casual git user I imagine the process normally goes something like this: Development happens. New feature makes it into the release version of git. New version makes it into the various linux distro repositories. People who run big git repos install the update. Serious nerds hear about it and use the feature. Many years pass. I learn about it, if it’s widely used enough.
minus-squarekus@programming.devlinkfedilinkEnglisharrow-up0·19 days agoThe big change in my opinion is we don’t need to tell newcomers about git checkout at all. Git switch --create is much better.
minus-squaretimbuck2themoon@sh.itjust.workslinkfedilinkEnglisharrow-up0·19 days agoI’m so old I still just use git checkout -b somebranch anyway.
Wait, git evolves?
it’s not recommended to boast about your ignorance.
Yep, whenever they fix a bug it’s added in a new flag that nobody knows about.
git --enable-sane-behaviour
As a casual git user I imagine the process normally goes something like this:
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.
I’m so old I still just use git checkout -b somebranch anyway.