Lines Matching refs:commit

26 with your patch series. It can build each individual commit and report
31 errors or image size increases in a particular commit or board to be
32 quickly identified and the offending commit pinpointed. This can be a big
64 commit). It is possible to build a branch for one board, then later build it
65 for another board. If you want buildman to re-build a commit it has already
69 It shows which commit introduced which board failure using a simple
71 case it is de-duped and displayed against the commit that introduced the
75 from commit to commit. An example of this is below.
78 a time. A thread starts at the first commit, configures the source for your
79 board and builds it. Then it checks out the next commit and does an
80 incremental build. Eventually the thread reaches the last commit and stops.
82 after every commit, and your build will be very slow. This is because a
88 output files in the working directory, organised by commit name and board
101 builds the upstream commit as well, for comparison. It cannot build
513 Total boards to build for each commit: 1059
523 directories for each commit and board.
539 This means that it is building 19062 board/commit combinations. So far it
581 is never fixed by a later commit, or you would see lubbock again, in green,
604 should be enough to work out what that commit is doing to break these
608 by that commit. Sometimes commits can be in the wrong order, so that a
613 At commit 16, the error moves: you can see that the old error at line 120
679 series is not supposed to change any other board. From commit 7 onwards the
690 --step 2 will show the image sizes for only every 2nd commit (so it will
694 only the upstream commit and your final branch commit.
822 This shows that commit 19 has reduced codesize for arm slightly and increased
926 commit for each board. This causes everything to be built from scratch. If you
970 differences in effective configuration between one commit and the next.
988 This shows that commit 44 enabled three new options for the board
989 am335x_evm_usbspl which were not enabled in commit 43. There is also a
1030 commit introduces an error in a particular board, buildman can easily show
1031 you this, even if a later commit fixes that error.
1062 buildman just shows a summary, with red indicating that a commit introduced
1063 an error and green indicating that a commit fixed an error. Use the -e
1117    -B shows which functions are growing/shrinking in which commit - great
1119    -S shows image sizes for each commit (just an overall summary)
1121    --step 0 will build just the upstream commit and the last commit of your