Specifically, each upload made with dgit must have as an ancestor the
current state of that package in the archive.
+I should expand a bit on the need for the git commit to be identical
+to the source package. dgit is (amongst other things) a way of
+looking at source packages, and their history, using git. That means
+that the git tree has to be the same as the package tree.
+Specifically, for example, files like configure need to either be in
+both git and the source package, or neither.
+
[ synthetic commit example ]
Non-dgit uploads don't have a (suitable) git commit hash. But