+So I think the real way to improve this is to persuade more
+maintainers to use dgit. Perhaps for maintainers who do not, we
+should at some point consider providing centrally an archive-based
+package history.
+
+
+But the most obvious challenge for a maintainer with an existing git
+branch, but trying to use dgit, is dgit's insistence that the source
+package and git tree are the same.
+
+However, some source packages contain files not in the maintainers'
+git branches, and which are needed to build: most commonly, autotools
+output. Such git branches are not useable with dgit.
+
+But nowadays most people recommend that the package build should
+always rerun autotools. If you do that, then neither your git tree
+nor your source package need contain the autotools output and all is
+well.
+
+Alternatively, you can commit the autotools output to git. Merge
+conflicts etc. are easily resolved by rerunning autotools.
+