From 7ba46bbf3be9e1bb01cfa50e46ec2f67a46b6eda Mon Sep 17 00:00:00 2001 From: Sean Whitton Date: Wed, 18 Apr 2018 16:39:19 -0700 Subject: dgit-maint-debrebase(7): correct what debrebase will do when debrebasing an NMU Signed-off-by: Sean Whitton --- dgit-maint-debrebase.7.pod | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'dgit-maint-debrebase.7.pod') 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 -- cgit v1.2.3