Skip to content

Conversation

@galisma
Copy link

@galisma galisma commented Oct 25, 2024

Hi, it has come to my attention that certain contributors are being removed for being born in the wrong country. IMHO this isn't enough. To achieve true political correctness we should ban contributors from all countries I personally dislike.

List of countries to be banned from contributing to the kernel:

Full List
Egypt
Cape Verde
Kyrgyzstan
Lithuania
Maldives
Tanzania
Myanmar
Jamaica
Malta
Benin
Dominican Republic
Congo
Solomon Islands
Cameroon
Vanuatu
Eritrea
New Zealand
Ghana
Grenada
Andorra
Colombia
Jordan
Algeria
Bulgaria
Thailand
Malaysia
Uganda
Paraguay
Finland
Bahamas
Zambia
South Africa
Timor-Leste
Belgium
Bahrain
Panama
R̶u̶s̶s̶i̶a (already banned)
Nigeria
Haiti
Australia
United Arab Emirates
Barbados
Holy See
Spain (the best country)
Equatorial Guinea
Czechia
Palau
Laos
Sweden
Gambia
Angola
Senegal
Kiribati
Costa Rica
Liberia
Canada
Togo
Iraq
Yemen
Greece
Democratic Republic of the Congo
Austria
Syria
Gabon
Cyprus
Uzbekistan
Lebanon
Liechtenstein
Chad
Trinidad and Tobago
Marshall Islands
Malawi
Central African Republic
Israel (for... reasons)
Madagascar
Luxembourg
Brazil
Romania
Mali
North Korea
Armenia
Sudan
Botswana
Samoa
Saudi Arabia
Guinea
Tonga
Rwanda
Netherlands
Monaco
Morocco
Turkey
Brunei
Bhutan
Philippines
Ecuador
Nicaragua
Italy
Ethiopia
Afghanistan
Saint Kitts and Nevis
India
Cambodia
Uruguay
Qatar
Serbia
Saint Lucia
Libya
Pakistan
France (please 🙏🏻)
Djibouti
Germany
Bangladesh
Micronesia
Guinea-Bissau
Kazakhstan
Hungary
Poland
Dominica
Sao Tome and Principe
South Korea
Mauritania
Guyana
Eswatini
Suriname
Slovakia
Oman
Niger
Singapore
Denmark
Belarus
Bosnia and Herzegovina
Sierra Leone
Cuba
Ireland
Côte d'Ivoire
Burundi
Ukraine
Papua New Guinea
Mauritius
Antigua and Barbuda
Saint Vincent and the Grenadines
Fiji
Portugal
Somalia
Kuwait
Nauru
Argentina
Latvia
Estonia
Chile
Moldova
Turkmenistan
Georgia
United States of America
Nepal
El Salvador
Venezuela
State of Palestine
North Macedonia
Tunisia
Croatia
Iceland
Japan
Slovenia
Kenya
Lesotho
Guatemala
Switzerland
Tuvalu
United Kingdom
China (你好谷歌翻译)
San Marino
Namibia
Vietnam
Norway
Honduras
Mozambique
Peru
Zimbabwe
Albania
Belize
South Sudan
Burkina Faso
Mongolia
Mexico
Comoros
Azerbaijan
Bolivia
Iran
Tajikistan
Montenegro
Indonesia
Seychelles
Sri Lanka

/s

Removed entries from countries I dislike
@KernelPRBot
Copy link

Hi @galisma!

Thanks for your contribution to the Linux kernel!

Linux kernel development happens on mailing lists, rather than on GitHub - this GitHub repository is a read-only mirror that isn't used for accepting contributions. So that your change can become part of Linux, please email it to us as a patch.

Sending patches isn't quite as simple as sending a pull request, but fortunately it is a well documented process.

Here's what to do:

  • Format your contribution according to kernel requirements
  • Decide who to send your contribution to
  • Set up your system to send your contribution as an email
  • Send your contribution and wait for feedback

How do I format my contribution?

The Linux kernel community is notoriously picky about how contributions are formatted and sent. Fortunately, they have documented their expectations.

Firstly, all contributions need to be formatted as patches. A patch is a plain text document showing the change you want to make to the code, and documenting why it is a good idea.

You can create patches with git format-patch.

Secondly, patches need 'commit messages', which is the human-friendly documentation explaining what the change is and why it's necessary.

Thirdly, changes have some technical requirements. There is a Linux kernel coding style, and there are licensing requirements you need to comply with.

Both of these are documented in the Submitting Patches documentation that is part of the kernel.

Note that you will almost certainly have to modify your existing git commits to satisfy these requirements. Don't worry: there are many guides on the internet for doing this.

Where do I send my contribution?

The Linux kernel is composed of a number of subsystems. These subsystems are maintained by different people, and have different mailing lists where they discuss proposed changes.

If you don't already know what subsystem your change belongs to, the get_maintainer.pl script in the kernel source can help you.

get_maintainer.pl will take the patch or patches you created in the previous step, and tell you who is responsible for them, and what mailing lists are used. You can also take a look at the MAINTAINERS file by hand.

Make sure that your list of recipients includes a mailing list. If you can't find a more specific mailing list, then LKML - the Linux Kernel Mailing List - is the place to send your patches.

It's not usually necessary to subscribe to the mailing list before you send the patches, but if you're interested in kernel development, subscribing to a subsystem mailing list is a good idea. (At this point, you probably don't need to subscribe to LKML - it is a very high traffic list with about a thousand messages per day, which is often not useful for beginners.)

How do I send my contribution?

Use git send-email, which will ensure that your patches are formatted in the standard manner. In order to use git send-email, you'll need to configure git to use your SMTP email server.

For more information about using git send-email, look at the Git documentation or type git help send-email. There are a number of useful guides and tutorials about git send-email that can be found on the internet.

How do I get help if I'm stuck?

Firstly, don't get discouraged! There are an enormous number of resources on the internet, and many kernel developers who would like to see you succeed.

Many issues - especially about how to use certain tools - can be resolved by using your favourite internet search engine.

If you can't find an answer, there are a few places you can turn:

If you get really, really stuck, you could try the owners of this bot, @daxtens and @ajdlinux. Please be aware that we do have full-time jobs, so we are almost certainly the slowest way to get answers!

I sent my patch - now what?

You wait.

You can check that your email has been received by checking the mailing list archives for the mailing list you sent your patch to. Messages may not be received instantly, so be patient. Kernel developers are generally very busy people, so it may take a few weeks before your patch is looked at.

Then, you keep waiting. Three things may happen:

  • You might get a response to your email. Often these will be comments, which may require you to make changes to your patch, or explain why your way is the best way. You should respond to these comments, and you may need to submit another revision of your patch to address the issues raised.
  • Your patch might be merged into the subsystem tree. Code that becomes part of Linux isn't merged into the main repository straight away - it first goes into the subsystem tree, which is managed by the subsystem maintainer. It is then batched up with a number of other changes sent to Linus for inclusion. (This process is described in some detail in the kernel development process guide).
  • Your patch might be ignored completely. This happens sometimes - don't take it personally. Here's what to do:
    • Wait a bit more - patches often take several weeks to get a response; more if they were sent at a busy time.
    • Kernel developers often silently ignore patches that break the rules. Check for obvious violations of the Submitting Patches guidelines, the style guidelines, and any other documentation you can find about your subsystem. Check that you're sending your patch to the right place.
    • Try again later. When you resend it, don't add angry commentary, as that will get your patch ignored. It might also get you silently blacklisted.

Further information

Happy hacking!

This message was posted by a bot - if you have any questions or suggestions, please talk to my owners, @ajdlinux and @daxtens, or raise an issue at https://github.com/ajdlinux/KernelPRBot.

@akuleshov7
Copy link

You have a conflict in this PR, please resolve it and then feel free to merge it. LGTM.

@KibaGasteiz
Copy link

The list should be just France.

@larryw3i
Copy link

I completely extremely exceedingly enormously agree with you.

@teatonedev
Copy link

Its okay. But not enough. I think you should also include some specific creature species to be banned.

@chunzha1
Copy link

To avoid internal collusion, should people from other countries who have traveled to these countries also be banned?

@SakuraRK
Copy link

My opinions:
Create a country, just name it Linux, And ONLY this country's citizen to contribution THIS repository.
I want to add Linus to this country's first citizen, And Identity system.

Copy link

@waltercool waltercool left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved

@arthurus36
Copy link

what beef do u have with france man

@galisma galisma closed this by deleting the head repository Nov 11, 2024
@github-staff github-staff deleted a comment Mar 26, 2025
@github-staff github-staff deleted a comment Mar 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants