chiark
/
gitweb
/
~ianmdlvl
/
dgit.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
| inline |
side by side
(parent:
9f04e19
)
dgit-maint-debrebase(7): correct what debrebase will do when debrebasing an NMU
author
Sean Whitton
<spwhitton@spwhitton.name>
Wed, 18 Apr 2018 23:39:19 +0000
(16:39 -0700)
committer
Sean Whitton
<spwhitton@spwhitton.name>
Thu, 19 Apr 2018 16:43:59 +0000
(09:43 -0700)
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
dgit-maint-debrebase.7.pod
patch
|
blob
|
history
diff --git
a/dgit-maint-debrebase.7.pod
b/dgit-maint-debrebase.7.pod
index a2ae3f8911cd0a8544fd820f74f6956a91db3de0..f5023e849ba5c6c271069e713a929bdf9c3974a4 100644
(file)
--- 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