dgit-badcommit-fixup; In --check mode, exit status 2 if things are not fine

[dgit.git] / debian / changelog

diff --git a/debian/changelog b/debian/changelog
index be2c165343cd5cdd5703f14f9208afbaeae54b80..003b00edbd5f915ccbf15d4aba7de826ac3eb69c 100644 (file)
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,9 +1,33 @@
-dgit (2.16~) unstable; urgency=medium
+dgit (2.16.2~) unstable; urgency=medium
 
-  * 
+  dgit-badcommit-fixup: 
+  * Fix crash when running for 2nd time in bare repo.
+  * In --check mode, exit with status 2 if things are not fine.
 
  --
 
+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: