Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
A repo to push patches to for reviewing
Shell Perl
Branch: master

Merge pull request #33 from karianna/master

Fixes from feedback of Phil Race of 2d team
latest commit 2e97266b58
@karianna karianna authored
Failed to load latest commit information.
1-unreviewed/javac_warnings/core/java/util Approved
2-duplicates Moved patches to new structure
2-further_review_needed Moved patches to new structure
2-rejected Moved patches to new structure
3-reviewed Fixes from Phil Race of 2d team
4-packaged Add some README.md files
6-accepted OpenJDK patches applied or already applied
6-already_applied/javac_warnings OpenJDK patches applied or already applied
bin adds license header information and copyright notices to scripts
.gitignore Gitignore
LICENSE license GPLv2 with CLASSPATH exception
README.md Fix typos in README.md
contributors.md

README.md

PatchReview

Git directory for reviewing warnings fix patches in the openjdk.

Process

  1. Fork the main repository (AdoptOpenJDK/PatchReview)
  2. Patches to be reviewed should be committed to the unreviewed directory.
  3. Review a patch, following the guidelines at http://java.net/projects/jugs/pages/AdoptOpenJDK/
  4. Feel free to make trivial changes if that helps get the patch through (although still note down the author of the patch to tell them what you changed and why).
  5. If approved, move the reviewed patch to the reviewed directory
  6. If the patch has already been applied to the OpenJDK codebase by someone else, move it to the beaten directory
  7. If the patch is inappropriate for some reason, move it to the rejected directory with a comment as to why you rejected the patch.
  8. Commit, writing a comment in the git commit message, comment should either be "Approved" or "2nd opinion requested".
  9. If you need a second review on a patch then put it in the 'further_review_needed' directory
  10. Rinse and repeat per patch (you can group patch reviews in a single commit, but make sure that this is grouped sensibly, try to to mix rejected with approved etc)
  11. Submit a pull request so that someone else can double check your work
Something went wrong with that request. Please try again.