Commit access and try branches

diff --git a/README_DEVELOPERS b/README_DEVELOPERS
index 5b0a1bc6adba6db2d746c61c140fe4c48e72ffb1..4ed21a561bb8e8840947c87258da85dc5b3e4fb6 100644 (file)
--- a/README_DEVELOPERS
+++ b/README_DEVELOPERS
@@ -80,6 +80,33 @@ compare them on all the performance tests:
   perl perf/vg_perf --vg=../trunk1 --vg=../trunk2 perf/
 
 
+Commit access and try branches
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+To get commit access to the valgrind git repository on sourceware
+you will have to ask an existing developer and fill in the following
+form: https://sourceware.org/cgi-bin/pdw/ps_form.cgi
+
+Every developer with commit access can use try branches. Code committed
+to a try branch will be build by the buildbot at builder.sourceware.org
+https://builder.sourceware.org/buildbot/#/builders?tags=valgrind-try
+
+If you want to try a commit you can push to a special named try branch
+(users/<your-user-name>/try-<topic>) as follows: 
+
+  git checkout -b frob
+  ...hack, hack, hack... OK, looks good to submit
+  git commit -a -m "Awesome hack"
+  git push origin frob:users/username/try-frob
+
+When all builders have build your patch the buildbot will sent you (or
+actually the patch author) an email telling you if any builds failed and
+references to all the logs. You can also find the logs and the builds here:
+https://builder.sourceware.org/buildbot/#/builders?tags=valgrind-try
+
+Afterwards you can delete the branch again:
+
+    git push origin :users/username/try-frob 
+
 Debugging Valgrind with GDB
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 To debug the valgrind launcher program (<prefix>/bin/valgrind) just