![]() ![]() Patches can actually be submitted via git on the command line. You can and should reply in multiple places as well. Hit ‘reply-all’, then expand the full reply message, scroll down to the part of the previous message or patch that you want to reply to, and write your post there. To make it obvious what your message is specifically in response to, your messages should be placed underneath the previous email. If you fail to turn on plain text mode, your email will likely be rejected.Ĭonversation on the mailing list is formatted a little different from normal email conversations. The mailing lists require you to only use plain text as opposed to HTML. You should always feel safe to be part of the linux community and accept that you’re allowed to make mistakes. There is a code of conduct that absolutely should be followed and enforced. I haven’t experienced any toxicity but have seen evidence of it. The linux kernel community has a bad reputation. The UX of the mailing list via gmail labels/filters Participating in conversation Code of conduct I create a label (via settings), and add filters like so: There are a few ways to organize this, but I like to have each mailing list in their own label and not in my inbox. Once you subscribe to a mailing list, your inbox will quickly be consumed by a deluge of emails. You can find instructions here for subscribing, but essentially you want to send an email to with the body of your email saying only subscribe (where list name would be replaced by something like ‘bpf’). You can find the many lists for the various subsystem communities here. You can subscribe to the mailing list of your choice using majordomo (a mailing list manager). It’s an intimidating system so let’s dive into how to start using it. You send an email to the mailing list, and then everyone who is subscribed to the mailing list gets your email. ![]() Mailing lists are not much more than an email forwarder. Mailing lists are where kernel developers discuss ideas, and submit patches. Once you know what subsystem community you’d like to be a part of, you can find the correspond mailing list. It’s a huge task to keep track of this whole system at once but luckily as an individual contributor, you don’t need to. Eventually the forks pull down the changes from other downstream forks. All these patches eventually make their way up to the ‘mainline’ kernel which a single maintainer presides over. The fork maintainers review these patches, and at regular intervals submit groups of patches ‘upstream’ to more generalized forks. ![]() Contributors submit relevant patches to the ‘mailing list’ that is used for each of these forks. Development happens in these forks for very specific subsystems, only a fraction of the overall code. Instead there are many forks of the linux kernel. Linux development does not happen in a single github repository, and likely never will. It has tens of thousands of contributors from all around the world, from many different companies and communities. The Linux kernel is the biggest open source project in existence. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |