'\" -*- coding: UTF-8 -*-
.if \n(.g .ds T< \\FC
.if \n(.g .ds T> \\F[\n[.fam]]
.de URL
\\$2 \(la\\$1\(ra\\$3
..
.if \n(.g .mso www.tmac
.TH gbp-pristine-tar 1 "1 February 2021" "" "git-buildpackage Manual"
.SH NAME
gbp-pristine-tar \- Manage pristine-tar commits in a git repository
.SH SYNOPSIS
'nh
.fi
.ad l
\fBgbp\ pristine-tar\fR \kx
.if (\nx>(\n(.l/2)) .nr x (\n(.l/5)
'in \n(.iu+\nxu
[\fB--version\fR] [\fB--help\fR] [\fB--verbose\fR] [\fB--color=\fR[auto|on|off]] [\fB--color-scheme=\fR \fICOLOR_SCHEME\fR] [\fB--upstream-tag=\fR \fItag-format\fR] [\fB--component=\fR \fIcomponent\fR]\&... \fBcommit\fR \fIfilename\fR 
'in \n(.iu-\nxu
.ad b
'hy
.SH DESCRIPTION
\fBgbp\ pristine-tar\fR adds the pristine-tar commit for a given
upstream tarball to a Git repository. This can be useful if a
original tarball has been already imported and the pristine-tar
commits should be added at a later time or if you're tracking
upstream git and want to create pristine-tar commits
nevertheless.
.SH OPTIONS
.TP 
\*(T<\fB\-\-version\fR\*(T>
Print version of the program, i.e. version of the git-buildpackage
suite
.TP 
\*(T<\fB\-v\fR\*(T>, \*(T<\fB\-\-verbose\fR\*(T>
Verbose execution
.TP 
\*(T<\fB\-h\fR\*(T>, \*(T<\fB\-\-help\fR\*(T>
Print help and exit
.TP 
\*(T<\fB\-\-color=\fR\*(T>[auto|on|off] 
Whether to use colored output.
.TP 
\*(T<\fB\-\-color\-scheme=\fR\*(T>\fICOLOR_SCHEME\fR 
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,
\*(T<\fB\-\-git\-color\-scheme=\fR\*(T>\*(T<'cyan:34::'\*(T> would
show debug messages in cyan, info messages in blue and other messages
in default (i.e. warning and error messages in red).
.TP 
\*(T<\fB\-\-upstream\-tag=\fR\*(T>\fItag-format\fR 
use this tag format when tagging upstream versions,
default is \fIupstream/%(version)s\fR
.TP 
\*(T<\fB\-\-component=\fR\*(T>\fICOMPONENT\fR 
When creating the pristine-tar commits also look for an additional tarball
with component name \fICOMPONENT\fR. E.g. in
\*(T<\fIhello\-debhelper_1.0.orig\-foo.tar.gz\fR\*(T>
the component name would be \fIfoo\fR. The additional
tarball is expected to be in the same directory than the upstream tarball
and to use the same compression type. This option can be
given multiple times to add multiple additional tarballs.

Using additional original tarballs is a feature of the 3.0
(quilt) source format. See
the \fBdpkg-source\fR manpage for
details. This is currently considered an experimental
feature and might change incompatibly.
.SH EXAMPLES
Add pristine-tar commits for an upstream tarball:
.PP
.nf
\*(T<
      \fBgbp\ pristine\-tar\fR commit ../upstream\-tarball\-0.1.tar.gz\*(T>
.fi
.PP
Same as above with an additional
tarball \*(T<\fI../upstream\-tarball\-foo\-0.1.tar.gz:\fR\*(T>
.PP
.nf
\*(T<
      \fBgbp\ pristine\-tar\fR \-\-component\-tarball=foo commit ../upstream\-tarball\-0.1.tar.gz\*(T>
.fi
.SH "CONFIGURATION FILES"
Several \*(T<\fIgbp.conf\fR\*(T> files are parsed 
to set defaults for the above command-line arguments. See the
\fBgbp.conf\fR(5) manpage for details.
.SH "SEE ALSO"
\fBgbp-import-orig\fR(1),
\fBgbp.conf\fR(5),
\fBdebuild\fR(1),
\fBgit\fR(1),
\fBpristine-tar\fR(1),
.URL file:///usr/share/doc/git-buildpackage/manual-html/index.html "       The Git-Buildpackage Manual"
.SH AUTHOR
Guido G\(:unther <\*(T<agx@sigxcpu.org\*(T>>