3 ms·

I would argue the "design goals" of git have evolved far past the kernel, which is a very unique and special project. These new patterns don't seem to invalida

I would argue the "design goals" of git have evolved far past the kernel, which is a very unique and special project. These new patterns don't seem to invalidate how the kernel uses git and they offer a lot of ergonomics in a Github-styled atmosphere. Are the only downsides that 1) users don't understand how kernel development is done, which extends far beyond source control; and 2) a merge commit is left as a marker?

Sir_Cmpwn 8y ago
It's not really about the kernel, the kernel is just where the world's most talented git experts work. The downsides include the creation of a merge commit, sure, but also the fact that it's used as a crutch by users who would rather not strive to understand how git works.