git-import-orig(1) Import an upstream source into a git repository


git-import-orig [ --verbose ] [ --upstream-version=version ] [ --no-merge ] [ --upstream-branch=branch_name ] [ --debian-branch=branch_name ] [ --[no-]sign-tags ] [ --keyid=gpg-keyid ] [ --upstream-tag=tag-format ] [ --filter=pattern ] [ --[no-]pristine-tar ] [ --[no-]filter-pristine-tar ] [ --postimport=cmd ] [ --uscan ] upstream-source


git-import-orig imports upstream-source into the Git repository. upstream-source can either be a gzip or bzip2 compressed tar archive or an already unpacked source tree. If it is already of the form package-name_version.orig.tar.gz, the version information is read from the tarball's filename otherwise it can be given on the command line via --upstream-version.

The sources are placed on the upstream branch (default: upstream), tagged and merged onto the debian branch (default: master).


The upstream version number
Don't merge the upstream version to the development branch
The branch in the Git repository the upstream sources are put onto. Default is upstream.
The branch in the Git repository the Debian package is being developed on, default is master. After importing the new sources on the upstream branch, git-import-orig will try to merge the new version onto this branch.
verbose execution
GPG sign all created tags
use this keyid for gpg signing tags
use this tag format when tagging upstream versions, default is upstream/<version>
use this format string for the commit message when importing upstream versions, default is Imported Upstream version %(version)s
filter out files glob-matching pattern. Can be given multiple times.
generate pristine-tar delta file
if using a filter also filter the files out of the tarball passed to pristine tar
run cmd after the import.
Use uscan to fetch new upstream version.


Four configuration files are parsed to set defaults for the above commandline arguments:

system wide configuraton
per user configuration
per branch configuration, can be published with the repository
per branch configuration, can be published with the repository
per repository configuration

See /etc/git-buildpackage/gbp.conf for an example.


Guido Guenther <[email protected]>