X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=dgit.git;a=blobdiff_plain;f=dgit-maint-debrebase.7.pod;h=e78f5f28eaf220ae2b0f3650149c710ec81bd9cf;hp=b17833e2353c422ea8619421b31faa77dc06d39d;hb=0df581dab31cc84a16974992d3c449197a2c00b3;hpb=0824695592eda56d0505f891aaf18db40958f0d7

diff --git a/dgit-maint-debrebase.7.pod b/dgit-maint-debrebase.7.pod
index b17833e2..e78f5f28 100644
--- a/dgit-maint-debrebase.7.pod
+++ b/dgit-maint-debrebase.7.pod
@@ -559,16 +559,23 @@ 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
-maintain a separate 'upstream' branch (unless you also happen to be
-involved in upstream development).  We work with upstream tags rather
-than any branches, except temporary branches used to prepare patches
-for forwarding upstream, for example.
+Except in the case where upstream releases only tarballs, or we
+require DFSG filtering, we do not maintain a separate 'upstream'
+branch (unless you also happen to be involved in upstream
+development).  We work with upstream tags rather than any branches
+(except temporary branches used to prepare patches for forwarding
+upstream, for example).
 
-The thought behind this is that from Debian's point of view, upstream
-releases are immutable points in history, better represented by tags.
+The idea here is that from Debian's point of view, upstream releases
+are immutable points in history, and so better represented by tags.
 
 =head2 The first ever dgit push