If you are submitting code, please have a look at the Coding Guidelines page .
Please keep some things in mind when preparing your patches for submission:
Submitting your changes via patch is a good thing. It may seem like an extra bit of work to create a patch and post it to the mailing list, or to make your work available in a public git repo, but there are good reasons why Open Source works that way:
Generating patches depends on the method you used to get the source code.
cd barry-work ./buildgen.sh cleanall cd .. diff -ruN barry-orig barry-work > patchfile
cd barry-cvs ./buildgen.sh cleanall cvs diff -u > patchfile grep ^? patchfileAny new files that you've added to your tree will need to be attached to your patch email, as CVS has no way to add files without write access to the repository.
cd barry-git git format-patch origin/master
Submitting changes can happen in one of three methods:
The git repo site repo.or.cz lets anyone create a forked tree based off the official Barry repo. This saves space on repo.or.cz, and adds your fork to a list at the bottom of the official Barry page.
This way, users and developers can look at everyone's changes and test and mix them as needed.
To create a forked tree, visit the Barry repo and click "fork" at the top.
The public git repository service at repo.or.cz provides an interesting feature, which allows anyone to push to a "mob" branch of a repository, if so configured by the admin.
It would go something like this:
# clone with mob user git clone git+ssh://mob@repo.or.cz/srv/git/barry.git barry cd barry git checkout -b mob origin/mob git diff origin/master..mob # make sure master == mob <make changes> git add ... && git commit git push origin mob <send email to the list, include the SHA1 sum of the commit>
This is a novel idea, as well as a security risk for anyone who blindly runs whatever is in the mob branch. Hence the recommended diff check above, to make sure you're working on an official branch.
The mob user can only push to the mob branch, so all other branches are read-only, and have been reviewed at least once by the project maintainer.
But the mob branch frees people up to use git, who may not have their own hosting, or who may not want to bother setting up their own git repo. People can use it to collaborate on a feature as well. Let your imagination run wild.
You can read more about the ideas behind the mob branch at the repo.or.cz mob page