git-debpush: Don't pretend to support --baredebian+tarball

[dgit.git] / git-debpush.1.pod

diff --git a/git-debpush.1.pod b/git-debpush.1.pod
index 926e8cd3faeedffda81962b120c6ac0d2e2268aa..2ce7013a511cb541d60a5e5a91331c81138051a0 100644 (file)
--- a/git-debpush.1.pod
+++ b/git-debpush.1.pod
@@ -109,11 +109,6 @@ You are using git-dpm(1)'s branch format.
 You are using the 'bare debian' branch format, with the upstream
 source in the form of an upstream tag.
 
-=item B<--quilt=baredebian+tarball>|B<--baredebian+tarball>
-
-You are using the 'bare debian' branch format, with the upstream
-source in the form of a tarball.
-
 =item B<--quilt=linear>
 
 You are using the 'manually maintained applied' branch format or
@@ -168,6 +163,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,
+B<git-debpush> needs a tag for the upstream part of your package.
+
+By default B<git-debpush> asks git-deborig(1),
+which searches for a suitable tag
+based on the upstream version in debian/changelog.
+
 =item B<--remote=>I<REMOTE>
 
 Where to push tags and branches.  If unspecified, use the remote which