Submit the patch by sending an email to collectd's mailinglist at Mails sent by non-subscribers will be held for approval.Generate the patch with diff -pur, as outlined above.Do a make distclean to clean up the generated files.
Git checkout -b foo/branch foo/branch-originĪfter making your changes to the "foo/branch"-branch you will need to create a (set of) patch(es) and send them in: Then you create a copy of that branch (here it's named "foo/branch"), to which you will make your changes: Git fetch origin foo/branch:foo/branch-origin To do this, you need to first fetch the branch into your local copy of the repository (here the local branch has the name "foo/branch-origin"): It's possible that you're asked to make your changes against a certain branch of the repository. If you're new to Git you might want to read the following documents to get started: Please note that many team members rely heavily on Github's issue and PR tracker and it may take a while until somebody looks at a patch from the mailing list. Please send them directly to collectd's mailing list at Mails sent by non-subscribers will be held for approval which will typically happen within 24 hours. Git clone git:///collectd/collectd.gitĪfter you made your changes you can send them in using the normal git-format-patch(1) and git-send-email(1) procedure. You can clone the repository anonymously via: You then pull this repository to your workstation:Īfter you've made your changes and pushed them to Github, go to your copy of the collectd repository on the Github website and create a Pull Request (PR) from there. Of course the first step is "cloning" collectd's Git repository: Go to and click on the "Fork" button. If you don't have an account there already, we recomend you create one. First of all, these days development of collectd is organized on Github.