path: root/git-debrebase.1.pod
diff options
authorIan Jackson <>2018-04-23 00:32:43 +0100
committerIan Jackson <>2018-06-16 22:40:13 +0100
commit6b3cdcf0d595efd96bc8c4220df87f7fd5aaef76 (patch)
treebd3c750df0facbea69e2e23c10f810c010fa456e /git-debrebase.1.pod
parent759d9092784d1aea335bd277e930c8f50ef0a493 (diff)
git-debrebase: Implement make-patches
Signed-off-by: Ian Jackson <>
Diffstat (limited to 'git-debrebase.1.pod')
1 files changed, 21 insertions, 0 deletions
diff --git a/git-debrebase.1.pod b/git-debrebase.1.pod
index 9f82a7c..5da5320 100644
--- a/git-debrebase.1.pod
+++ b/git-debrebase.1.pod
@@ -188,6 +188,27 @@ that its command line syntax is optimal.
We may want to introduce an incompatible replacement syntax
under the name C<new-upstream>.
+=item git-debrebase make-patches
+Generate patches in debian/patches/
+representing the changes made to upstream files.
+It is not normally necessary to run this command explicitly.
+When uploading to Debian,
+dgit and git-debrebase
+will cooperate to regenerate patches as necessary.
+When working with pure git remotes,
+the patches are not needed.
+Normally git-debrebase make-patches will
+require a laundered branch.
+(A laundered branch does not contain any patches.)
+But if there are already some patches made by
+git-debrebase make-patches,
+and all that has happened is that more
+changes to upstream files have been committed,
+running it again can add the missing patches.
=item git-debrebase convert-from-gbp [<upstream-commit-ish>]
Cnnverts a gbp patches-unapplied branch