Contributing

We take fixes

How do I write good patches?

Explain the problem that your change solves. Explain why your change solves the problem well. If applicable, explain how you tested the patch, and give us a way of reproducing the issue.

Before Before making the patch, make sure your system is up to date.

Make your code match the rest of the system. Look at style(6) for a summary of our code style.

If your patch includes new features or flags, be sure to update the documentation.

If the patch is intrusive or significantly changes the design of aspects of the system, it may be worth discussing it first. Email works for this, but IRC works better.

How do I send in my patches?

To send changes, email 9front@9front.org with your patch attached inline.

Generate the patch using:

% bind -ac /dist/plan9front /
% cd /sys/src/your/changed/code
% git/diff . > /tmp/mypatch.diff

% git/export $commit

Paste the change into your email client of choice. Inline patches are preferred, but beware: The gmail web interface mangles them, replacing tabs with spaces. If you must use the gmail web interface, attach the patch.

This project is run by hobbyists. It may take some time for people to respond. If you don't hear anything for more than a week or so, send a ping.