From 5d005f403cca2f8c8212811dd15271e03c18a515 Mon Sep 17 00:00:00 2001
From: Michael Stapelberg <michael@stapelberg.de>
Date: Sun, 22 Sep 2013 00:08:27 +0200
Subject: [PATCH] man/i3-dump-log: document -f (Thanks TonyC)

---
 man/i3-dump-log.man | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/man/i3-dump-log.man b/man/i3-dump-log.man
index eb8ba2f76..455144071 100644
--- a/man/i3-dump-log.man
+++ b/man/i3-dump-log.man
@@ -1,7 +1,7 @@
 i3-dump-log(1)
 ==============
-Michael Stapelberg <michael+i3@stapelberg.de>
-v4.1, December 2011
+Michael Stapelberg <michael@i3wm.org>
+v4.6, September 2013
 
 == NAME
 
@@ -9,7 +9,7 @@ i3-dump-log - dumps the i3 SHM log
 
 == SYNOPSIS
 
-i3-dump-log [-s <socketpath>]
+i3-dump-log [-s <socketpath>] [-f]
 
 == DESCRIPTION
 
@@ -19,6 +19,9 @@ figuring out what is going on, without permanently logging to a file.
 
 With i3-dump-log, you can dump the SHM log to stdout.
 
+The -f flag works like tail -f, i.e. the process does not terminate after
+dumping the log, but prints new lines as they appear.
+
 == EXAMPLE
 
 i3-dump-log | gzip -9 > /tmp/i3-log.gz