summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSean Whitton <spwhitton@spwhitton.name>2018-04-19 09:19:55 -0700
committerSean Whitton <spwhitton@spwhitton.name>2018-04-19 09:43:59 -0700
commit944f532e615c416a2dd16a617f948b2f89a6f0de (patch)
tree306d111e0b7b774dd721f2ef9f07d3c212698079
parent0824695592eda56d0505f891aaf18db40958f0d7 (diff)
dgit-maint-debrebase(7): further notes about d/patches
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
-rw-r--r--dgit-maint-debrebase.7.pod6
1 files changed, 6 insertions, 0 deletions
diff --git a/dgit-maint-debrebase.7.pod b/dgit-maint-debrebase.7.pod
index b17833e..6d14c0b 100644
--- a/dgit-maint-debrebase.7.pod
+++ b/dgit-maint-debrebase.7.pod
@@ -559,6 +559,12 @@ git-debrebase(1). You should not make changes there. They will
either cause trouble, or be ignored and overwritten by
git-debrebase(1).
+I<debian/patches> will often be out-of-date because git-debrebase(1)
+will only regenerate it when it needs to. So you should not rely on
+the information in that directory. When preparing patches to forward
+upstream, you should use git-format-patch(1) on git commits, rather
+than sending files from I<debian/patches>.
+
=head2 Upstream branches
Except in the case where upstream releases only tarballs, we do not