.\" This manpage has been automatically generated by docbook2man 
.\" from a DocBook document.  This tool can be found at:
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
.\" Please send any bug reports, improvements, comments, patches, 
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "GBP-PQ" "1" "01 June 2012" "" "git-buildpackage Manual"

.SH NAME
gbp-pq \- Manage quilt patches on patch queue branches in git
.SH SYNOPSIS

\fBgbp-pq\fR [ \fB--verbose\fR ] [ \fB--color=\fI[auto|on|off]\fB\fR ] [ \fB--[no-]patch-numbers\fR ] [ \fB--topic=\fItopic\fB\fR ] [ \fB--time-machine=\fInum\fB\fR ] \fBdrop\fR | \fBexport\fR | \fBimport\fR | \fBrebase\fR | \fBswitch\fR

.SH "DESCRIPTION"
.PP
\fBgbp-pq\fR helps one to manage quilt patches in Debian packages that are maintained
with \fBgit-buildpackage\fR\&. This is especially useful with packages using the
3.0 (quilt) source format. With \fBgbp-pq\fR you can maintain the quilt patches
that should be applied to a package on a separate branch called patch-queue
branch. So if your Debian package lives on \fImaster\fR
the associated patch-queue branch will be called
\fIpatch-queue/master\fR\&.
.PP
See  <URL:https://honk.sigxcpu.org/piki/development/debian_packages_in_git/> for example workflows.
.SH "ACTIONS"
.TP
\fBimport \fR
Create a patch queue branch from quilt patches in debian/patches/ that
are listed in debian/patches/series.
.TP
\fBexport \fR
Export the patches on the patch-queue branch associated to the current
branch into a quilt patch series in debian/patches/ and update the
series file.
.TP
\fBrebase \fR
Switch to the patch-queue branch associated to the current branch and
rebase it against the current branch.
.TP
\fBdrop \fR
Drop (delete) the patch queue associated to the current branch. So if
you're on branch \fIfoo\fR this would drop branch
\fIpatch-queue/foo\fR\&.
.TP
\fBapply \fR
Add a single patch to the patch-queue similar to using
\fBgit-am\fR\&. Use \fB--topic\fR if you want
the patch to appear in a separate subdir when exporting the patch queue
using \fBexport\fR\&. This can be used to separate upstream
pathes from debian specific patches.
.TP
\fBswitch \fR
Switch to the patch-queue branch if on the base branch and switch
to base branch if on patch-queue branch.
.SH "OPTIONS"
.TP
\fB--verbose\fR
.TP
\fB-v\fR
verbose execution
.TP
\fB--color=\fI[auto|on|off]\fB \fR
Whether to use colored output.
.TP
\fB--[no-]patch-numbers \fR
Whether the patch files should start with a number or not.
.TP
\fB--topic=\fItopic\fB \fR
Topic to use when importing a single patch
.TP
\fB--time-machine=\fINUM\fB \fR
When importing a patch queue fails, go back commit by
commit on the current branch to check if the patch-queue applies
there. Do this at most \fINUM\fR times. This can
be useful if the patch-queue doesn't apply to the current branch HEAD
anymore, e.g.  after importing a new upstream version.
.SH "TAGS"
.PP
When exporting patches from a patch-queue branch \fBgbp-pq\fR will look at the
patch header for special tags it recognizes. All tags need to start at the
first column and require at least one whitespace after the colon.
.TP
\fBGbp-Pq-Topic: \fItopic\fB\fR
Moves the patch into a subdir called
\fItopic\fR when running 

.nf
\fBgbp-pq\fR
	  export
.fi
\&. This allows for some structure below
\fIdebian/patches\fR\&. 
.SH "SEE ALSO"
.PP
\fBgit-buildpackage\fR(1),
\fBdpkg-source\fR(1),
\fBquilt\fR(1),
\fBgbp.conf\fR(5)
.SH "AUTHOR"
.PP
Guido Guenther <agx@sigxcpu.org>