From ba5cd1c4f1dc3a274462bf6cfe9195617cd7461b Mon Sep 17 00:00:00 2001
From: Ali Servet Donmez <asd@pittle.org>
Date: Tue, 7 Jun 2016 09:42:13 +0200
Subject: [PATCH] Use log instead of whatchanged

As per documentation (https://git-scm.com/docs/git-whatchanged):

"New users are encouraged to use git-log(1) instead. The whatchanged command is essentially the same as git-log(1) but defaults to show the raw format diff output and to skip merges.

The command is kept primarily for historical reasons; fingers of many people who learned Git long before git log was invented by reading Linux kernel mailing list are trained to type it."
---
 tips.json | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/tips.json b/tips.json
index dfffb7a..d3cad05 100644
--- a/tips.json
+++ b/tips.json
@@ -89,7 +89,8 @@
     "tip": "curl http://git.io/vfhol > ~/.git-completion.bash && echo '[ -f ~/.git-completion.bash ] && . ~/.git-completion.bash' >> ~/.bashrc"
 }, {
     "title": "What changed since two weeks?",
-    "tip": "git whatchanged --since='2 weeks ago'"
+    "tip": "git log --no-merges --raw --since='2 weeks ago'",
+    "alternatives": ["git whatchanged --since='2 weeks ago'"]
 }, {
     "title": "See all commits made since forking from master",
     "tip": "git log --no-merges --stat --reverse master.."