petsoi@discuss.tchncs.de to Linux@programming.dev · 1 day agoGit 2.48 releasedgithub.blogexternal-linkmessage-square11fedilinkarrow-up175arrow-down11cross-posted to: [email protected]
arrow-up174arrow-down1external-linkGit 2.48 releasedgithub.blogpetsoi@discuss.tchncs.de to Linux@programming.dev · 1 day agomessage-square11fedilinkcross-posted to: [email protected]
minus-squarekbal@fedia.iolinkfedilinkarrow-up2·18 hours 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-up1·3 hours 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-up2·2 hours agoI’m so old I still just use git checkout -b somebranch anyway.
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.