path: root/dgit-maint-debrebase.7.pod
diff options
authorSean Whitton <>2018-04-18 16:39:19 -0700
committerSean Whitton <>2018-04-19 09:43:59 -0700
commit7ba46bbf3be9e1bb01cfa50e46ec2f67a46b6eda (patch)
treed9a801fa77d75e7cf64b337923453b32a19a8bf8 /dgit-maint-debrebase.7.pod
parent9f04e19a184b812d8643b6e712bf4106648ca7bf (diff)
dgit-maint-debrebase(7): correct what debrebase will do when debrebasing an NMU
Signed-off-by: Sean Whitton <>
Diffstat (limited to 'dgit-maint-debrebase.7.pod')
1 files changed, 2 insertions, 2 deletions
diff --git a/dgit-maint-debrebase.7.pod b/dgit-maint-debrebase.7.pod
index a2ae3f8..f5023e8 100644
--- a/dgit-maint-debrebase.7.pod
+++ b/dgit-maint-debrebase.7.pod
@@ -488,8 +488,8 @@ If the NMUer added new commits modifying the upstream source, you will
probably want to debrebase before your next upload to tidy those up.
For example, the NMUer might have used git-revert(1) to unapply one of
-your patches. A debrebase will strip both the patch and the reversion
-from the delta queue.
+your patches. A debrebase can be used to strip both the patch and the
+reversion from the delta queue.
=head2 Manually applying the debdiff