A very comfortable way of posting changes for review is ReviewBoard, where every project repository has its own entry.
To create your changeset, you probably want to work in a separate branch - or even in your clone. This is actually suggested and the proper way to do changesets in Git. You can create any number of commits, amend them, and do whatever you want to do - it won't affect the next steps, as you will submit the whole branch for review.
Before proceeding it is good practice to rebase your branch onto the branch you want to target for the merge. So, supposing you want to target master, make sure it is up-to-date with the remote and then run, and want to publish a review for a local branch:
git rebase master
If you want to post a review for merging a non local branch, you might want to run the following:
git merge master
Once you are done with the above, it is time to post the changes to ReviewBoard. The easiest and most comfortable way to do that is post-review, a handy command line tool which takes care of creating review requests for you.
The following has to be done only once to make your local clone fit for use with post-review.
First of all, you have to tell it about the ReviewBoard server. If your project does not ship with a .reviewboardrc file (encourage the project manager to add one!), the first thing you have to run is:
git config reviewboard.url https://git.reviewboard.kde.org
ReviewBoard currently only knows the project repositories by their git:// URLs, making it necessary to have a remote using the git:// URL in your clone. If your origin remote is already using the git:// URL, you are all set. If not you need to add another remote now.
Let's suppose you are looking to have some changes to Amarok reviewed, and the URL of your origin remote is email@example.com:amarok. To add another remote using the git:// URL you might run:
git remote add anonupstream git://anongit.kde.org/amarok git fetch anonupstream
If your origin remote was already using the git:// url, substitute anonupstream with origin throughout the rest of this tutorial.
You are now ready to create the review request. The post-review command should look something like this:
post-review --parent=master --tracking-branch=anonupstream/master
This command tells post-review that your branch is based upon master, and it is set to track the remote branch anonupstream/master. You can also give post-review some more arguments to avoid using the web interface later - have a look at the user manual for more on that.
After the command has been run a web address will be shown in the terminal, pointing at your review request.
If you need to update an existing review request you can invoke post-review with an additional -r argument, which should be the numeric id of the review request you want to update. Supposing you want to update review request 54, you would run:
post-review --parent=master --tracking-branch=anonupstream/master -r 54
In some rare cases you simply want to generate a diff and submit it to ReviewBoard later. You can do that by running:
post-review --parent=master -n > your-patch.patch
To close a review request, you can either use the ReviewBoard web interface or more conveniently, right in a commit. This is done by using the REVIEW keyword followed by the review ID you want to close. For example, to close review 54, you would put
in your commit. A message will also be posted to ReviewBoard indicating the commit SHA1 that closed the request.
One popular way of submitting patches is KDE's reviewboard. A big advantage over using the bugtracker of KDE is that the patches are less likely to be forgotten here. Also, the reviewboard allows inline review of diffs and other gimmicks.
First you need to check if the project you've created the patch for is actually using reviewboard. For this, go to the groups section and see if the project's group is listed there. If it is listed there, you should use the reviewboard, otherwise send the patch by other means.
For sending a patch, you first need to register. Then simply click New Review Request and fill out the form. The most important parts of the form are:
After you completed the form, a notification mail will be sent to the developers and they will answer you.
/!\ You need to use svn diff in english, if your system is not english, please do LC_ALL=C svn diff