From: Nicholas Nethercote Date: Wed, 26 Apr 2023 07:00:32 +0000 (+1000) Subject: Clarify try push instructions. X-Git-Tag: VALGRIND_3_21_0~8 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=15313a558081755a783dcf2e3db0e155b3b4fbd2;p=thirdparty%2Fvalgrind.git Clarify try push instructions. --- diff --git a/README_DEVELOPERS b/README_DEVELOPERS index 979ee13b4a..5b93b1c870 100644 --- a/README_DEVELOPERS +++ b/README_DEVELOPERS @@ -87,26 +87,21 @@ 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 +Every developer with commit access can use try branches. If you want to try a +branch before pushing you can push to a special named try branch as follows: -If you want to try a commit you can push to a special named try branch -(users//try-) as follows: + git push origin $BRANCH:users/$USERNAME/try-$BRANCH - git checkout -b - ...hack, hack, hack... OK, looks good to submit - git commit -a -m "Awesome hack" - git push origin :users//try- +Where $BRANCH is the branch name and $USERNAME is your user name. -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: +You can see the status of the builders here: https://builder.sourceware.org/buildbot/#/builders?tags=valgrind-try +The buildbot will also sent the patch author multiple success/failure emails. + Afterwards you can delete the branch again: - git push origin :users/username/try- + git push origin :users/$USERNAME/try-$BRANCH Debugging Valgrind with GDB