and not, in general, reversible,
so dgit operates on the principle that
the dgit git history contains the actual contents of the package.
+(When dgit is manipulating a .dsc,
+it does so in a private area,
+where the transforming gitattributes are defused (disabled),
+to achieve this.)
If transforming gitattributes used,
they can cause trouble,
because the working tree files can differ from
the git revision history
(and therefore from the source packages).
+
+So dgit clone
+and dgit setup-new-tree
+disable transforming gitattributes
+by default,
+by creating a .git/info/attributes.
+When fetching or importing sources
+dgit warns if it finds .gitattributes file
+and the transforming gitattributes have not been defused
+(e.g. in the case of a tree not made with dgit clone).
+
+See
+.B dgit setup-new-tree
+and
+.B dgit setup-gitattributes
+in dgit(1).
.SH PACKAGE SOURCE FORMATS
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