chiark / gitweb /
dgit-maint-debrebase(7): Drop bad advice about upstream/ tag case
authorSean Whitton <spwhitton@spwhitton.name>
Wed, 27 May 2020 20:57:47 +0000 (13:57 -0700)
committerSean Whitton <spwhitton@spwhitton.name>
Thu, 28 May 2020 00:36:16 +0000 (17:36 -0700)
The first argument to the new-upstream subcommand is a version number,
not a tag name, so this instruction could never have been correct.

The user should not need usually to pass both the upstream version
number and the upstream/ tag name, either, because git-debrebase
should find it for them.

Reported-by: David Bremner <bremner@debian.org>
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
Acked-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
dgit-maint-debrebase.7.pod

index 373fb2f7aa335456d09aee970e4d4f05b4972021..fdbf2e8d70b9da58d6afab8972496b2cb5949067 100644 (file)
@@ -394,8 +394,6 @@ or if you have a working watch file
 
 =back
 
-replacing I<1.2.3> with I<upstream/1.2.3> if you imported a tarball.
-
 This invocation of git-debrebase(1) involves a git rebase.  You may
 need to resolve conflicts if the Debian delta queue does not apply
 cleanly to the new upstream source.