petsoi@discuss.tchncs.de to Linux@programming.dev · 10 天前Git 2.48 releasedgithub.blogexternal-linkmessage-square12fedilinkarrow-up185arrow-down11cross-posted to: git@programming.dev
arrow-up184arrow-down1external-linkGit 2.48 releasedgithub.blogpetsoi@discuss.tchncs.de to Linux@programming.dev · 10 天前message-square12fedilinkcross-posted to: git@programming.dev
minus-squareFizzyOrange@programming.devlinkfedilinkarrow-up16arrow-down1·9 天前Yep, whenever they fix a bug it’s added in a new flag that nobody knows about. git --enable-sane-behaviour
minus-squarekbal@fedia.iolinkfedilinkarrow-up6·9 天前As 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-up1·9 天前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.
minus-squaretimbuck2themoon@sh.itjust.workslinkfedilinkEnglisharrow-up2·9 天前I’m so old I still just use git checkout -b somebranch anyway.
minus-squarefoenkyfjutschah@programming.devlinkfedilinkarrow-up6arrow-down22·10 天前it’s not recommended to boast about your ignorance.
Wait, git evolves?
Yep, whenever they fix a bug it’s added in a new flag that nobody knows about.
git --enable-sane-behaviourAs 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.
U are the only one who knows my pain
it’s not recommended to boast about your ignorance.