path: root/dgit.7
diff options
authorIan Jackson <>2018-01-24 23:45:57 +0000
committerIan Jackson <>2018-01-24 23:46:02 +0000
commit6e65361c03015f933a393ad8667c0fb0dd0b6adf (patch)
tree2f1eb57ac4431bb0e89ea0b5599e7e3341b0ee14 /dgit.7
parentef2804f8817f5d2771caa1c70a9ebe4591268099 (diff)
dgit(7): Discuss file executability.
Signed-off-by: Ian Jackson <>
Diffstat (limited to 'dgit.7')
1 files changed, 13 insertions, 0 deletions
diff --git a/dgit.7 b/dgit.7
index 70165a1..ca11535 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.
+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.
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