infra: dgit-mirror-ssh-wrap: Fix $package_re

[dgit.git] / dgit.1

diff --git a/dgit.1 b/dgit.1
index 8969e2f24c45b94c53553539e286af31873a894d..f7c06d06fa0648c9f12525deb434f135a42dd725 100644 (file)
--- a/dgit.1
+++ b/dgit.1
@@ -1293,6 +1293,13 @@ The result is a fresh import,
 discarding the git history
 that the person who pushed that .dsc was working with.
 .TP
 discarding the git history
 that the person who pushed that .dsc was working with.
 .TP

+.B \-\-force-reusing-version
+Carry on even though this involves reusing a version number
+of a previous push or upload.
+It is normally best to give different versions different numbers.
+Some servers (including, usually, the Debian server)
+will reject attempts to reuse or replace already-pushed versions.
+.TP

 .B \-\-force-uploading-binaries
 Carry on and
 upload binaries
 .B \-\-force-uploading-binaries
 Carry on and
 upload binaries


@@ -1333,7 +1340,7 @@ See Debian bug #841867.
 .BR \-\-for\-push
 Override the dgit-distro.distro.readonly configuration setting,
 to specify that we have read/write access
 .BR \-\-for\-push
 Override the dgit-distro.distro.readonly configuration setting,
 to specify that we have read/write access

-and should use the corresponding git and achive access approach
+and should use the corresponding git and achieve access approach

 even if the operation is a read-only one.
 .SH CONFIGURATION
 dgit can be configured via the git config system.
 even if the operation is a read-only one.
 .SH CONFIGURATION
 dgit can be configured via the git config system.