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. 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.

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. 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. Git format-patch -o output-directory -s foo/branch-origin.foo/branch I'll outline the typical steps one does when making the changes:Ĭp -r collectd-version collectd-version- mineĭiff -pur collectd-version collectd-version- mine >collectd-version- mine.patch If you don't want to work out the complexities of Git (or you read this page after you made the changes ) you can take some release (at best the latest one) and make your changes there. Extract the source code and make a copy of the entire directory.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.

Ftfh kasumi rebirth download