X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=dgit.git;a=blobdiff_plain;f=dgit.7;h=ca1153522b5bce81e7b32166a76b52123ba4041e;hp=70165a1b69d0d9f745ae6e2f2a92135f985a8870;hb=6e65361c03015f933a393ad8667c0fb0dd0b6adf;hpb=ef2804f8817f5d2771caa1c70a9ebe4591268099

diff --git a/dgit.7 b/dgit.7
index 70165a1b..ca115352 100644
--- a/dgit.7
+++ b/dgit.7
@@ -243,6 +243,19 @@ If you are not the maintainer, you do not need to worry about the
 source format of the package.  You can just make changes as you like
 in git.  If the package is a `3.0 (quilt)' package, the patch stack
 will usually not be represented in the git history.
+.SH FILE EXECUTABILITY
+Debian source package formats
+do not always faithfully reproduce
+changes to executability.
+But dgit insists that the result of dgit clone is identical
+(as far as git can represent - see Limitations, above)
+to the result of dpkg-source -x.
+
+So files that are executable in your git tree
+must be executable in the result of dpkg-source -x
+(but often aren't).
+If a package has such troublesome files,
+they have to be non-executable in dgit-compatible git branches.
 .SH FORMAT 3.0 (QUILT)
 For a format `3.0 (quilt)' source package, dgit may have to make a
 commit on your current branch to contain metadata used by quilt and