As I have become to understand this problem from dozens of articles that have been written about it. Yes, you can't remove code from a previous release, that i

As I have become to understand this problem from dozens of articles that have been written about it. Yes, you can't remove code from a previous release, that is even technically impossible with the mix of different releases being in production and forks and derived works. But what you can do is remove your code from the source, the living document from which these releases are produced, practically removing your contribution from subsequent releases. This has to be possible since it's technically probable that old code is removed from source by the author or replaced by someone else, and this happens all the time during development. But what really makes me sad, is that every article written lately has focused on developer reaction and whether it is right or wrong. One author even pulled a quote from Ian Malcolm's character from Jurassic Park, lamenting that we are preoccupied with if it is possible to do so, not if we should do so. But failing to critically scrutinize the source of the problem, mainly the CoC and the peddlers of this document. It's not a question if the Kernel community could or could not adopt it, but ask should it be adopted at all. It seems like the adoption of the new CoC is a foregone conclusion not up for debate, and now we are forced to argue in circles over the impact of this document since all talk regarding the adoption of CoC is forbidden.