Release v1.2.0

README.md

@@ -158,7 +158,7 @@ If you don't have an internal apt server, you can use `dpkg -i` to install the
 One possibility is with the following commands in your Dockerfile:
 
 ```Dockerfile
-RUN wget https://github.com/Yelp/dumb-init/releases/download/v1.1.3/dumb-init_1.1.3_amd64.deb
+RUN wget https://github.com/Yelp/dumb-init/releases/download/v1.2.0/dumb-init_1.2.0_amd64.deb
 RUN dpkg -i dumb-init_*.deb
 ```
 
@@ -169,7 +169,7 @@ Since dumb-init is released as a statically-linked binary, you can usually just
 plop it into your images. Here's an example of doing that in a Dockerfile:
 
 ```Dockerfile
-RUN wget -O /usr/local/bin/dumb-init https://github.com/Yelp/dumb-init/releases/download/v1.1.3/dumb-init_1.1.3_amd64
+RUN wget -O /usr/local/bin/dumb-init https://github.com/Yelp/dumb-init/releases/download/v1.2.0/dumb-init_1.2.0_amd64
 RUN chmod +x /usr/local/bin/dumb-init
 ```
 

VERSION

@@ -1 +1 @@
-1.1.3
+1.2.0

VERSION.h

@@ -1,6 +1,6 @@
 // THIS FILE IS AUTOMATICALLY GENERATED
 // Run `make VERSION.h` to update it after modifying VERSION.
 unsigned char VERSION[] = {
-  0x31, 0x2e, 0x31, 0x2e, 0x33, 0x0a
+  0x31, 0x2e, 0x32, 0x2e, 0x30, 0x0a
 };
 unsigned int VERSION_len = 6;

debian/changelog

@@ -1,3 +1,16 @@
+dumb-init (1.2.0) unstable; urgency=medium
+
+  * Hand the controlling TTY to the child process, if we have one (#122).
+
+    This fixes warnings that are printed when running a typical command like:
+        docker run -ti <image> dumb-init bash
+    ...as well as allowing you to use job control.
+
+    Thanks to @ehlers for the patch, and @alhafoudh (and several others) for
+    reporting the issue and providing details!
+
+ -- Chris Kuehl <[email protected]>  Mon, 10 Oct 2016 14:09:57 -0700
+
 dumb-init (1.1.3) unstable; urgency=low
 
   * Add support for FreeBSD kernel. Thanks @onlyjob for bringing this to our