&dhemail;
&dhfirstname;
&dhsurname;
gbp-pq
&dhsection;
gbp-pqManage quilt patches on patch queue branches in git
&gbp-pq;
&man.common.options.synopsis;
topicnumDESCRIPTION
&gbp-pq; helps one to manage quilt patches in Debian packages that are
maintained with &gbp;. This is especially useful with packages using the
3.0 (quilt) source format. With &gbp-pq; 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
master the associated patch-queue branch will be
called patch-queue/master.
See
for example workflows.
ACTIONS
Create a patch queue branch from quilt patches in debian/patches/
that are listed in debian/patches/series. The patches must apply
without fuzz.
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.
Switch to the patch-queue branch associated to the current branch and
rebase it against the current branch.
Drop (delete) the patch queue associated to the current branch. So if
you're on branch foo this would drop
branch patch-queue/foo.
Add a single patch to the patch-queue similar to using
git-am. Use if you want
the patch to appear in a separate subdir when exporting the patch queue
using . This can be used to separate upstream
pathes from debian specific patches.
Switch to the patch-queue branch if on the base branch and switch
to base branch if on patch-queue branch.
OPTIONS
&man.common.options.description;
Whether the patch files should start with a number or not.
topic
Topic to use when importing a single patch
NUM
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 NUM 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.
Whether to drop (delete) the patch queue branch after
a succesful exportIn case of import even import if the branch already
existsTAGS
When exporting patches from a patch-queue branch &gbp-pq; 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.
Ignores the commit, no patch is generated out of it.
topic
Moves the patch into a subdir called topic
when running &gbp-pq; export This allows for some
structure below debian/patches.
topic
Deprecated: use
topic instead.
SEE ALSO,
dpkg-source1,
quilt1,
AUTHOR
&dhusername; &dhemail;