From 17a40e188aec062573f9f65a59062496e1d06bde Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=D0=94=D0=B0=D0=BC=D1=98=D0=B0=D0=BD=20=D0=93=D0=B5=D0=BE?=
 =?UTF-8?q?=D1=80=D0=B3=D0=B8=D0=B5=D0=B2=D1=81=D0=BA=D0=B8?=
 <gdamjan@gmail.com>
Date: Thu, 5 Jul 2018 17:57:12 +0200
Subject: [PATCH] forgot the second point

---
 src/channel.rs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/channel.rs b/src/channel.rs
index c14c28d..5caaecd 100644
--- a/src/channel.rs
+++ b/src/channel.rs
@@ -24,7 +24,7 @@ pub fn run_tar_in_thread(path: PathBuf) -> futures::sync::mpsc::UnboundedReceive
  *
  *   there are 2 features important about futures::sync::mpsc
  *       - it works with tokio (and so with actix), so the stream is async friendly
- *       -
+ *       - it can be sent across threads (more importantly, the tx part)
  *   cons:
  *       futures::sync::mpsc::unbounded() is unbounded, which means the tar thread will
  *       just push everything in memory as fast as it can (as cpu allows).