On Sat, Oct 22, 2011 at 10:03 AM, Freddie Chopin <freddie_cho...@op.pl> wrote: > So that's normal that all patchsets now are marked as "not verified" ("X") > because the build fails at a file completely unaffected by that patch and > unchanged for a long time (buspirate.c for example)?
"all" you have to do, is to rebase your fix on top of the other fix that's in the queue and push. Then your patch will go green. # Copy this from the patchset w/buspirate fix: $ git fetch http://openocd.zylin.com/p/openocd refs/changes/43/43/3 && git checkout FETCH_HEAD From http://openocd.zylin.com/p/openocd * branch refs/changes/43/43/3 -> FETCH_HEAD Previous HEAD position was ae675e5... Fix "Evaluate 'script' in the global scope" HEAD is now at 593c8de... buspirate: ignore return value and fix warning # checkout your path fix git checkout ae675e5 Previous HEAD position was 593c8de... buspirate: ignore return value and fix warning HEAD is now at ae675e5... Fix "Evaluate 'script' in the global scope" # rebase your patch on top of the buspirate warning fix $ git rebase 593c8de First, rewinding head to replay your work on top of it... Applying: Fix "Evaluate 'script' in the global scope" # Push updated patch! oyvind@titan:~/workspace/openocd$ git push review Stand back... and your patch should go green... -- Øyvind Harboe - Can Zylin Consulting help on your project? US toll free 1-866-980-3434 http://www.zylin.com/ _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development