-dgit (2.14) unstable; urgency=low
+dgit (2.16.1) UNRELEASED; urgency=medium
- *
+ * dgit-badcommit-fixup: New mode --check which is readonly.
- --
+ -- Ian Jackson <ijackson@chiark.greenend.org.uk> Sat, 07 Jan 2017 13:04:49 +0000
+
+dgit (2.16) unstable; urgency=low
+
+ Dealing with fallout from #849041:
+ * Provide dgit-badcommit-fixup history-rewriting script.
+ * New rewrite map feature, which allows dgit git server to adjust
+ clients' interpretation of Dgit fields, so that history-rewriting is
+ effective. (Feature is only partially implemented right now -
+ enough to dig current Debian users out of the hole.) Re:#850431.
+
+ Test suite:
+ * New test case for history-rewriting.
+ * Change `local foo=$(bar)' idiom to `local foo; foo=$(bar)' since
+ the former does not trip set -e even if bar fails :-(.
+
+ -- Ian Jackson <ijackson@chiark.greenend.org.uk> Fri, 06 Jan 2017 20:46:30 +0000
+
+dgit (2.15) UNRELEASED; urgency=high
+
+ Infastructure:
+ * Prevent introduction of new commits which lack `committer'
+ information. Ie, prevent the reception of new commits afflicted by
+ #849041. Existing commits are tolerated.
+
+ Test suite:
+ * Be much stricter about messages from git-fsck.
+
+ -- Ian Jackson <ijackson@chiark.greenend.org.uk> Thu, 05 Jan 2017 18:20:23 +0000
+
+dgit (2.14) unstable; urgency=critical
+
+ CRITICAL BUGFIX:
+ * Do not generate bogus commits with --overwrite or import-dsc.
+ Closes:#849041.
+
+ Test suite:
+ * Run a lot of git-fsck.
+
+ -- Ian Jackson <ijackson@chiark.greenend.org.uk> Wed, 04 Jan 2017 22:52:55 +0000
dgit (2.13) unstable; urgency=high