| |||||||||||||
Where to rejected patches go?Where to rejected patches go?Posted Jul 2, 2010 7:33 UTC (Fri) by milki (guest, #68231)Parent article: SELF: Anatomy of an (alleged) failure
Btw, I've wondered this for a while. Back in 2.0 days, there was a small repository of applyable patches (iBCS2, PC speaker sound card emulation, dual monitor support and Co.), which weren't included in the mainline kernel. The externel hosting was never an official feature, though.
But what about today? Where do patches go if they are rejected? Is everything just thrown away?? Shouldn't there be a public review and archival repository somewhere? Or even a separate GIT for incoming patches? (Can't believe it's all sent per email.)
If use contributed patches don't make it INTO the kernel, it would help if they were at least AVAILABLE somewhere. Otherwise there is little chance for user lobbying, or at least patching your own kernel.
(Log in to post comments)
Where to rejected patches go? Posted Jul 6, 2010 9:35 UTC (Tue) by dlang (✭ supporter ✭, #313) [Link]
the biggest problem is that there is no one place where rejected patches are ever together today.
there are many ways patches can be sent, to many different people (and in some cases the patches themselves aren't sent, just a request to pull from a git repository that may disappear in a few days)
it would be a significant amount of work to gather such patches, let alone maintain them.
there are patches like this today, but they get hosted and maintained by the people who care about them.
|
|||||||||||||