4 ms·
Linus Torvalds on some good git development practices
- gcv 17y agoThis post probably should be required reading for people moving from Subversion, since Subversion repositories almost never have clean history. I define "clean" as a history with all changes isolated by self-contained commits, and no "oops I forgot this one file" junk.
- CUViper 17y agoMy "unclean" peeve is when people prepare a git patch series with a separate commit for each file. If I can't apply the first M patches of your N patch series and have a usable tree, then you're doing it wrong.
- jrockway 17y agoHmm, I disagree. I have no qualms about rebasing my own public repository, although I wouldn't want someone else to do that. This seems like it is "approved", as git has code to handle a pull after a history rewrite... so I am not worried about it. There are few things more cumbersome than sending patches via email, especially when you have git.
- gruseom 17y agoThere are few things more cumbersome than sending patches via email, especially when you have git. Really? That's the only way my partner and I exchange code (git bundles rather than patches, but same idea).
- known 17y ago"By three methods we may learn wisdom: First, by reflection, which is noblest; Second, by imitation, which is easiest; and third by experience, which is the bitterest" --Unknown
- azharcs 17y agoquote is by Confucius. :)