Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

gbp-pull(1) [debian man page]

GBP-PULL(1)						      git-buildpackage Manual						       GBP-PULL(1)

NAME
gbp-pull - Safely update a repository from remote SYNOPSIS
gbp-pull [ --verbose ] [ --force ] [ --redo-pq ] [ --[no-]pristine-tar ] [ --debian-branch=branch_name ] [ --upstream-branch=branch_name ] [ --depth=depth ] DESCRIPTION
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. OPTIONS
--force force a branch update even if this results in a non fast forward update. Warning: Forcing a branch updates makes you lose your modifications. --redo-pq also rebuild the corresponding patch-queue using gbp-pq. Warning: This drops the patch-queue branch if it exists. --debian-branch=branch_name The branch in the Git repository the Debian package is being developed on, default is master. --upstream-branch=branch_name The branch in the Git repository the upstream sources are put onto. Default is upstream. --depth=depth Git history depth, for deepening shallow git clones. --verbose -v verbose execution --pristine-tar Whether to update the pristine-tar branch too. EXIT CODES
When gbp-pull finishes it indicates success or failure with it's exit code: 0 Success. 1 An error occured during the pull, see the printed error message for details. 2 At least one branch couldn't be fast forwarded. CONFIGURATION FILES
Several gbp.conf files are parsed to set defaults for the above commandline arguments. See the [XRef to GBP.MAN.GBP.CONF] manpage for details. SEE ALSO
git-buildpackage(1), gbp-clone(1), gbp-pq(1), gbp.conf(5) AUTHOR
Guido Guenther <agx@sigxcpu.org> 01 June 2012 GBP-PULL(1)

Check Out this Related Man Page

GIT-REQUEST-PULL(1)                                                 Git Manual                                                 GIT-REQUEST-PULL(1)

NAME
git-request-pull - Generates a summary of pending changes SYNOPSIS
git request-pull [-p] <start> <url> [<end>] DESCRIPTION
Generate a request asking your upstream project to pull changes into their tree. The request, printed to the standard output, begins with the branch description, summarizes the changes and indicates from where they can be pulled. The upstream project is expected to have the commit named by <start> and the output asks it to integrate the changes you made since that commit, up to the commit named by <end>, by visiting the repository named by <url>. OPTIONS
-p Include patch text in the output. <start> Commit to start at. This names a commit that is already in the upstream history. <url> The repository URL to be pulled from. <end> Commit to end at (defaults to HEAD). This names the commit at the tip of the history you are asking to be pulled. When the repository named by <url> has the commit at a tip of a ref that is different from the ref you have locally, you can use the <local>:<remote> syntax, to have its local name, a colon :, and its remote name. EXAMPLE
Imagine that you built your work on your master branch on top of the v1.0 release, and want it to be integrated to the project. First you push that change to your public repository for others to see: git push https://git.ko.xz/project master Then, you run this command: git request-pull v1.0 https://git.ko.xz/project master which will produce a request to the upstream, summarizing the changes between the v1.0 release and your master, to pull it from your public repository. If you pushed your change to a branch whose name is different from the one you have locally, e.g. git push https://git.ko.xz/project master:for-linus then you can ask that to be pulled with git request-pull v1.0 https://git.ko.xz/project master:for-linus GIT
Part of the git(1) suite Git 2.17.1 10/05/2018 GIT-REQUEST-PULL(1)
Man Page