Jann Horn
jann@infosec.exchange
The Linux kernel "every subsystem has its own git tree" thing is so annoying.
Especially when one file is plausibly associated with multiple subsystems and patches get routed through more than one.
I guess it probably works reasonably well for people who only ever touch stuff in the one subsystem they specialize in, but for anything else...
4
1
0
지지 ᚠᚱᛖᛃᚨ Daniel 黄法官 CyReVolt
CyReVolt@mastodon.social@jann ah yes, that is sometimes annoying.
Already discussed quite some years ago:
https://lwn.net/Articles/738235/
1
0
0
지지 ᚠᚱᛖᛃᚨ Daniel 黄法官 CyReVolt
CyReVolt@mastodon.social@jann and I literally ran into the same kinda issue just the other day:
https://github.com/kubernetes/website/pull/54363
though that is arguably way smaller, luckily, and people are discussing cross-subdir concerns.
0
0
0
Christian Brauner 🦊🐺
brauner@mastodon.social@jann I have a feeling this is a subpost and I want to know now about what exactly.
2
0
0
@jann Not to mention own rules, own preferences for when to submit patches, what type of things to worry about etc etc.
0
0
0
0
0
0
@brauner the trigger for me writing this post was that I wrote a cleanup patch on top of a subsystem's -next tree, sent it, then was informed that a similar patch has already been sitting in another subsystem tree for weeks...
0
0
0