3 ms·
See, switches in git are there because git maintains backward compatibility. Sometimes a switch really would logically be better as a whole new command. But it'
by sounds 10y ago
See, switches in git are there because git maintains backward compatibility. Sometimes a switch really would logically be better as a whole new command. But it's a common refrain to hear that git hides useful things in the switches.
This article is a great way to find those hidden things.
- masklinn 10y ago> See, switches in git are there because git maintains backward compatibility. Switches are there because git commands tend to greatly leak the abstraction and group behaviour in terms of the underlying plumbing, and because Git maintainers most likely would rather add new switches to existing commands than new commands intersecting with existing ones. > Sometimes a switch really would logically be better as a whole new command. Which could trivially be done without BC issues and thus can't be an explanation why existing commands keep growing new switches. > This article is a great way to find those hidden things. It would have been a useful article if it had been about showcasing interesting or useful git switches.
- aisofteng 10y agoAlternatively, read the documentation and know how to use your tools instead of reading blog posts that lists a few things one person has found useful.