From cea683ee43be6a625646d08d4ecbb40fa822e65c Mon Sep 17 00:00:00 2001
From: grossws <grossws@gmail.com>
Date: Thu, 9 Jul 2015 12:01:14 +0300
Subject: [PATCH] Use `&>` for redirecting stdout & stderr

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 327bdf6..f0c6f0e 100644
--- a/README.md
+++ b/README.md
@@ -121,7 +121,7 @@ Notes:
 
 - Know about "here documents" in Bash, as in `cat <<EOF ...`.
 
-- In Bash, redirect both standard output and standard error via: `some-command >logfile 2>&1`. Often, to ensure a command does not leave an open file handle to standard input, tying it to the terminal you are in, it is also good practice to add `</dev/null`.
+- In Bash, redirect both standard output and standard error via: `some-command &>logfile` (which means `some-command >logfile 2>&1`). Often, to ensure a command does not leave an open file handle to standard input, tying it to the terminal you are in, it is also good practice to add `</dev/null`.
 
 - Use `man ascii` for a good ASCII table, with hex and decimal values. For general encoding info, `man unicode`, `man utf-8`, and `man latin1` are helpful.