Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

git-import-dsc(1) [debian man page]

GIT-IMPORT-DSC(1)					      git-buildpackage Manual						 GIT-IMPORT-DSC(1)

git-import-dsc - Import Debian packages into a Git repository SYNOPSIS
git-import-dsc [ --verbose ] [ --upstream-branch=branch_name ] [ --debian-branch=branch_name ] [ --[no-]sign-tags ] [ --keyid=gpg-keyid ] [ --debian-tag=tag-format ] [ --upstream-tag=tag-format ] [ --filter=pattern ] [ --[no-]pristine-tar ] [ --download ] [ --allow-same-versions ] [ --author-is-committer ] [ --author-date-is-committer-date ] debian-source.dsc git-import-dsc [ options ] --download [ --[no-]allow-unauthenticated ] URL | source-package DESCRIPTION
git-import-dsc imports a Debian source package into a Git repository, notes the package version in the commit logs, and commits the change. All information, including package name, version, Debian diffs, and upstream source is automatically detected from the source package. OPTIONS
--upstream-branch=branch_name The branch in the Git repository the upstream sources are put onto. Default is upstream. --debian-branch=branch_name The branch in the Git repository the debian sources are put onto. Default is master. --verbose -v verbose execution --[no-]sign-tags GPG sign all created tags --keyid=gpg-keyid use this keyid for gpg signing tags --debian-tag=tag-format use this tag format when tagging Debian versions, default is debian/%(version)s --upstream-tag=tag-format use this tag format when tagging upstream versions, default is upstream/%(version)s --filter=pattern filter out files glob-matching pattern. Can be given multiple times. --pristine-tar generate pristine-tar delta file --download Download the source package instead of looking for it in the local file system. The argument can either be a source-package name or an URL. The former uses apt-get to download the source while the later uses dget. --allow-unauthenticated Whether to skip signature verification on downloads. --allow-same-version Allow to import a package with the same debian version. --author-is-committer When importing the Debian patch, use the author identity as comitter identity. --author-date-is-committer-date When importing the Debian patch, use the author date as comitter date. Warning: Git will subtly misbehave if the committer date of a commit is not later than or equal to all its parents. 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-import-dscs(1), git-buildpackage(1), git-import-orig(1), git-dch(1), apt-get(1), dget(1), gbp.conf(5), debuild(1), git(1), pristine- tar(1), The Git-Buildpackage Manual <URL:file:///usr/share/doc/git-buildpackage/manual-html/index.html> AUTHOR
Guido Guenther <> 01 June 2012 GIT-IMPORT-DSC(1)

Check Out this Related Man Page

GIT-CHERRY(1)							    Git Manual							     GIT-CHERRY(1)

git-cherry - Find commits not merged upstream SYNOPSIS
git cherry [-v] [<upstream> [<head> [<limit>]]] DESCRIPTION
The changeset (or "diff") of each commit between the fork-point and <head> is compared against each commit between the fork-point and <upstream>. The commits are compared with their patch id, obtained from the git patch-id program. Every commit that doesn't exist in the <upstream> branch has its id (sha1) reported, prefixed by a symbol. The ones that have equivalent change already in the <upstream> branch are prefixed with a minus (-) sign, and those that only exist in the <head> branch are prefixed with a plus (+) symbol: __*__*__*__*__> <upstream> / fork-point \__+__+__-__+__+__-__+__> <head> If a <limit> has been given then the commits along the <head> branch up to and including <limit> are not reported: __*__*__*__*__> <upstream> / fork-point \__*__*__<limit>__-__+__> <head> Because git cherry compares the changeset rather than the commit id (sha1), you can use git cherry to find out if a commit you made locally has been applied <upstream> under a different commit id. For example, this will happen if you're feeding patches <upstream> via email rather than pushing or pulling commits directly. OPTIONS
-v Verbose. <upstream> Upstream branch to compare against. Defaults to the first tracked remote branch, if available. <head> Working branch; defaults to HEAD. <limit> Do not report commits up to (and including) limit. SEE ALSO
git-patch-id(1) GIT
Part of the git(1) suite Git 11/24/2012 GIT-CHERRY(1)
Man Page

Featured Tech Videos