.\" 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-RPM" "1" "" "" "git-buildpackage Manual"

.SH NAME
gbp-pq-rpm \- Manage patches and development branches in Git
.SH SYNOPSIS

\fBgbp\~pq-rpm\fR [ \fB--version\fR ] [ \fB--help\fR ] [ \fB--verbose\fR ] [ \fB--color=\fI[auto|on|off]\fB\fR ] [ \fB--color-scheme=\fICOLOR_SCHEME\fB\fR ] [ \fB--packaging-dir=\fIDIRECTORY\fB\fR ] [ \fB--spec-file=\fIFILEPATH\fB\fR ] [ \fB--upstream-tag=\fITAG-FORMAT\fB\fR ] [ \fB--force\fR ] [ \fB--[no-]patch-numbers\fR ] \fBdrop\fR | \fBexport\fR | \fBimport\fR | \fBrebase\fR | \fBswitch\fR | \fBapply\fR

.SH "DESCRIPTION"
.PP
\fBgbp\~pq-rpm\fR helps in managing patches and development branch(es) for
packages that are maintained with \fBgbp\fR\&. It designed to be used for
packages that are maintained using the "orphan-packaging" model.
\fBgbp\~pq-rpm\fR has multiple subcommands, or actions, for working with the
branches and patches.
.PP
\fBgbp\~pq-rpm\fR makes it easy to do source code development on a separate
development branch (patch-queue branch in Debian git-buildpackage terms).
For example, if the packaging files would be stored in
\fImaster\fR the associated development branch would
be \fIdevelopment/master\fR\&.
.SH "ACTIONS"
.TP
\fBimport \fR
Create a development (patch-queue) branch by applying all patches
from the packaging branch on top of the upstream version. The patches
must apply without fuzz.
.TP
\fBexport \fR
Export patches from the development branch into the packaging branch.
It generates patches (one-per-commit) from the development branch and
updates the spec file accordingly. It doesn't automatically commit
the changes though - they need to verified and committed manually.
.TP
\fBrebase \fR
Switch to the development branch and rebase it against the current
upstream version (indicated in the spec file of the associated
packaging branch).
.TP
\fBdrop \fR
Drop (delete) the development branch associated to the current
branch. For example, you're on branch \fIfoo\fR
this would drop branch \fIdevelopment/foo\fR\&.
.TP
\fBapply \fR
Add a single patch to the development branch - similar to using
\fBgit-am\fR\&.
.TP
\fBswitch \fR
Switch between the development branch and the associated packaging
branch.
.SH "OPTIONS"
.TP
\fB--version\fR
Print version of the program, i.e. version of the git-buildpackage
suite
.TP
\fB-v\fR
.TP
\fB--verbose\fR
Verbose execution
.TP
\fB-h\fR
.TP
\fB--help\fR
Print help and exit
.TP
\fB--color=\fI[auto|on|off]\fB \fR
Whether to use colored output.
.TP
\fB--color-scheme=\fICOLOR_SCHEME\fB \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,
\fB--git-color-scheme=\fR\&'cyan:34::' would
show debug messages in cyan, info messages in blue and other messages
in default (i.e. warning and error messages in red).
.TP
\fB--packaging-dir=\fIDIRECTORY\fB \fR
Subdirectory that contains the RPM packaging files.
.TP
\fB--spec-file=\fIFILEPATH\fB \fR
Relative path to the spec file to use. Special value
\fIauto\fR causes \fBgbp\fR to search and guess.
Other values cause the \fB--packaging-dir\fR option to be
ignored: the directory of the spec file is used, instead.
.TP
\fB--upstream-tag=\fITAG-FORMAT\fB \fR
Use this tag format when looking for tags of upstream versions,
default is \fIupstream/%(version)s\fR\&.
.TP
\fB--force\fR
Import even if the development (patch-queue) branch already exists.
Only valid for the import action.
.TP
\fB--[no-]patch-numbers \fR
Whether the patch files should start with a number or not.
.SH "META TAGS"
.PP
When exporting patches from a patch-queue branch \fBgbp\~pq-rpm\fR will look at
the commit message 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-Rpm: Ignore \fR
Ignores the commit, no patch is generated out of it.
.TP
\fBGbp-Rpm: If <expression> \fR
Conditional patch. Put patch inside "%if <expression>" in the
spec file.
.TP
\fBGbp-Rpm: IfArch<expression> \fR
Conditional patch. Put patch inside "%ifarch <expression>" in
the spec file.
.PP
For example, the following commit message:

.nf
      Fix around a problem in Fedora

      which is not applicable elsewhere.

      Gbp-Rpm: If 0%{?fedora}
    
.fi
.PP
Will result something like this in the spec file:

.nf
      # 0001-Fix-around-a-problem-in-Fedora.patch
      %if 0%{?fedora}
      %patch0 -p1
      %endif
    
.fi
.SH "SEE ALSO"
.PP
\fBgbp-buildpackage-rpm\fR(1)>,
\fBgbp-import-srpm\fR(1)>,
\fBgbp.conf\fR(5)>
.SH "AUTHOR"
.PP
Markus Lehtonen <markus.lehtonen@linux.intel.com>