path: root/dgit.1
diff options
authorIan Jackson <>2016-09-25 14:48:41 +0100
committerIan Jackson <>2016-09-26 01:36:22 +0100
commit6a009a8fe0fa46c0d92d51300566c7afcf21ed2e (patch)
tree294b6334976cf711fe5eda17162a11fc18fbf402 /dgit.1
parent9103f4a18a893971b6ab8fab4c1ac4c98729eecb (diff)
Overwrite: Provide --overwrite=VERSION option
Signed-off-by: Ian Jackson <>
Diffstat (limited to 'dgit.1')
1 files changed, 22 insertions, 0 deletions
diff --git a/dgit.1 b/dgit.1
index 87ad0fc..8769f72 100644
--- a/dgit.1
+++ b/dgit.1
@@ -330,6 +330,28 @@ This can be useful with build, if you plan to commit later. (dgit
push will still ensure that the .dsc you upload and the git tree
you push are identical, so this option won't make broken pushes.)
+.BI --overwrite= previous-version
+Declare that even though your git branch is not a descendant of
+.IR previous-version
+according to the revision history, in fact, it really does contain
+all the (wanted) changes from that version.
+.I previous-version
+ought to be the version currently in the archive.
+dgit push will make a
+pseudo-merge (that is, something that looks like the result
+of git merge -s ours) to stitch the archive's version into your own
+git history, so that your push is a fast forward from the archive.
+This option is useful if you are the maintainer, and you have
+incorporated NMU changes into your own git workflow in way that
+doesn't make your branch a fast forward from the NMU.
+(In quilt mode
+.BR gbp ", " dpm " or " unpatched ,
+implying a split between the dgit view and the
+maintainer view, the pseudo-merge will appear only in the dgit view.)
.BI --deliberately- something
Declare that you are deliberately doing
.IR something .