Lines Matching refs:branch

10 - Creates patch directly from your branch
22 once, and keep the settings with each branch rather than having to
41 - Add tags into the commits within each branch to indicate where the
45 - Each branch tracks the upstream branch, so that this script can
47 - Check out a branch, and run this script to create and send out your
136 If it can't detect the upstream branch, try telling it how many patches
188 	patman does not yet use it, but it is convenient to put the branch
319 these rather contrived patches in the following order in branch us-cmd in
337 (if you are tracking an upstream branch):
446 1. When you change back to the us-cmd branch days or weeks later all your
455 compare change and see what you did, you can either create a new branch for
456 each version, or just tag the branch before you start changing it: