changelog: Mention #850519 re docs updates

[dgit.git] / dgit.1

diff --git a/dgit.1 b/dgit.1
index 0da57f57c9214e45e706aad6692e0645af1e4557..8cf3928ae9efeb0d519dd74a0425691df65ce0af 100644 (file)
--- a/dgit.1
+++ b/dgit.1
@@ -307,7 +307,6 @@ dgit will stop with an error message.
 If
 .I branch
 does not start with refs/, refs/heads/ is prepended.
-The specified branch is unconditionally updated.
 .TP
 .B dgit version
 Prints version information and exits.
@@ -417,7 +416,7 @@ 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.)
 .TP
-.BR --overwrite =\fIprevious-version\fR
+.BR --overwrite [=\fIprevious-version\fR]
 Declare that even though your git branch is not a descendant
 of the version in the archive
 according to the revision history,
@@ -488,7 +487,7 @@ if the .dsc names a git commit which has been rewritten
 by those in charge of the distro,
 this option may prevent that rewrite from being effective.
 Also,
-using it can mean that
+it can mean that
 dgit fails to find necessary git commits.
 .TP
 .BR --dgit-view-save= \fIbranch\fR|\fIref\fR
@@ -896,7 +895,7 @@ These options are provided as an escape hatch,
 in case dgit is confused.
 (They might also be useful for testing error cases.)
 .TP
-.B --import-dsc-with-dgit-field
+.B --force-import-dsc-with-dgit-field
 Tell dgit import-dsc to treat a .dsc with a Dgit field
 like one without it.
 The result is a fresh import,