Lines Matching refs:branch

62 can be run repeatedly on the same branch. In this case it will automatically
64 commit). It is possible to build a branch for one board, then later build it
100 Buildman generally builds a branch (with the -b flag), and in this case
103 branch. Put all your commits in a branch, set the branch's upstream to a
160 $ git checkout -b my-branch origin/master
161 $ # Add some commits to the branch, reading for testing
478 First do a dry run using the -n flag: (replace <branch> with a real, local
479 branch with a valid upstream)
481 $ ./tools/buildman/buildman -b <branch> -n
483 If it can't detect the upstream branch, try checking out the branch, and
484 doing something like 'git branch --set-upstream-to upstream/master'
485 or something similar. Buildman will try to guess a suitable upstream branch
494     5bb3505 Merge branch 'master' of git://git.denx.de/u-boot-arm
531 $ ./tools/buildman/buildman -b <branch>
551 01: Merge branch 'master' of git://git.denx.de/u-boot-arm
586 $ ./tools/buildman/buildman -b <branch> -se lubbock
694 only the upstream commit and your final branch commit.
914 You can build a range of commits by specifying a range instead of a branch
1069 You don't need to stick around on that branch while buildman is running. It
1082           ** buildman -b <branch> powerpc
1085           ** buildman -b <branch> esd
1088           ** buildman -b <branch> keymile siemens
1091           ** buildman -b <branch> mpc83xx freescale 4xx
1122         branch. This is often a quick sanity check that your branch doesn't