petsoi@discuss.tchncs.de to Linux@programming.dev · 1 day agoGit 2.48 releasedgithub.blogexternal-linkmessage-square9fedilinkarrow-up169arrow-down11cross-posted to: git@programming.dev
arrow-up168arrow-down1external-linkGit 2.48 releasedgithub.blogpetsoi@discuss.tchncs.de to Linux@programming.dev · 1 day agomessage-square9fedilinkcross-posted to: git@programming.dev
minus-squareFizzyOrange@programming.devlinkfedilinkarrow-up9·14 hours 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-up1·15 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-squareMauryamj@programming.devlinkfedilinkarrow-up1·16 hours agoU are the only one who knows my pain
minus-squarefoenkyfjutschah@programming.devlinkfedilinkarrow-up5arrow-down20·21 hours agoit’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-behaviour
As a casual git user I imagine the process normally goes something like this:
U are the only one who knows my pain
it’s not recommended to boast about your ignorance.