summaryrefslogtreecommitdiff
path: root/git-debpush.1.pod
diff options
context:
space:
mode:
authorIan Jackson <ijackson@chiark.greenend.org.uk>2019-07-06 23:54:54 +0100
committerIan Jackson <ijackson@chiark.greenend.org.uk>2019-07-07 11:18:17 +0100
commit4a6f56f6197d76a436c63a2794baf3808687fb2e (patch)
tree3530a9bf5d07494bee66fa89a5442e7e9a7ed2ed /git-debpush.1.pod
parent66f76f761bc38ab61dd068af4b9200b05002305b (diff)
git-debpush: Support --upstream=TAG (and document it)
Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
Diffstat (limited to 'git-debpush.1.pod')
-rw-r--r--git-debpush.1.pod9
1 files changed, 9 insertions, 0 deletions
diff --git a/git-debpush.1.pod b/git-debpush.1.pod
index 926e8cd..f1edf77 100644
--- a/git-debpush.1.pod
+++ b/git-debpush.1.pod
@@ -168,6 +168,15 @@ Note that this need not actually be a branch, but any committish (see
gitglossary(7)). The option name is chosen to fit what is by far the
most common case.
+=item B<--upstream=>I<TAG>
+
+When pushing a non-native package,
+git-debpush needs a tag for the upstream part of your package.
+
+By default git-debpush asks git-deborig,
+which searches for a suitable tag in your tree,
+based on the upstream version.
+
=item B<--remote=>I<REMOTE>
Where to push tags and branches. If unspecified, use the remote which