3 ms·
Now imagine that you had the "mess" each contributor produced in the course of development in the history of the Linux Kernel - instead of just a clean set of f
by chmod775 5y ago
Now imagine that you had the "mess" each contributor produced in the course of development in the history of the Linux Kernel - instead of just a clean set of final patches.
That's what git was written for.
On the other hand recording all the nitty gritty details might be nice for smaller projects.
- daniellarusso 5y agoI admit I have not looked at the kernel repo in quite awhile. Is rebase used with gitflow in that context?
- formerly_proven 5y agoThe kernel uses a patch-based workflow. Someone sends a bunch of patches to a list, gets feedback, improves on the patches, and sends the new set of patches. This might have added patches to the set, or changes to the existing patches. Repository write access is not (generally) shared between developers. This is a very, very different way of using git from how almost everyone else uses git.
- yoz-y 5y agoThe cool thing with git is that nothing is preventing you from doing the latter. For small personal projects I don’t even care about small commits.
- wyoung2 5y agoThat's section 2.5 in the same document: https://www.fossil-scm.org/home/doc/trunk/www/fossil-v-git.wiki#vs-linux https://www.fossil-scm.org/home/doc/trunk/www/fossil-v-git.w...