Provided by: git-buildpackage_0.7.2_all bug


       gbp-pull - Safely update a repository from remote


       gbp  pull  [  --version  ]  [  --help ] [ --verbose ] [ --color=[auto|on|off] ] [ --color-
       scheme=COLOR_SCHEME ] [ --force ] [ --redo-pq ] [ --[no-]pristine-tar ] [  --ignore-branch
       ] [ --debian-branch=branch_name ] [ --upstream-branch=branch_name ] [ --depth=depth ]


       gbp  pull  updates the debian, upstream and pristine-tar branches from a remote repository
       in one go. It checks if the update is safe (would result  in  a  fast-forward  merge)  and
       aborts otherwise.


              Print version of the program, i.e. version of the git-buildpackage suite


              Verbose execution


       --help Print help and exit

              Whether to use colored output.

              Colors  to  use  in  output (when color is enabled). The format for COLOR_SCHEME is
              '<debug>:<info>:<warning>:<error>'.  Numerical values and color names are accepted,
              empty  fields  imply the default color. For example, --git-color-scheme='cyan:34::'
              would show debug messages in cyan, info messages in  blue  and  other  messages  in
              default (i.e. warning and error messages in red).

              force a branch update even if this results in a non fast forward update.

              Warning: Forcing a branch update makes you lose your modifications.

              also rebuild the corresponding patch-queue using gbp pq.

              Warning: This drops the patch-queue branch if it exists.

              Don't care if we're on a branch or in detached head state.

              The  branch in the Git repository the Debian package is being developed on, default
              is master.

              The branch in the Git repository the upstream sources  are  put  onto.  Default  is

              Git history depth, for deepening shallow git clones.

              Whether to update the pristine-tar branch too.


       When gbp pull finishes, it indicates success or failure with its exit code:

       0      Success.

       1      An error occurred during the pull, see the printed error message for details.

       2      At least one branch couldn't be fast forwarded.


       Several  gbp.conf  files  are parsed to set defaults for the above command-line arguments.
       See the gbp.conf(5)> manpage for details.


       gbp-buildpackage(1)>, gbp-clone(1)>, gbp-pq(1)>, gbp.conf(5)>


       Guido Guenther <>

                                         29 January 2016                              GBP-PULL(1)