From 26f4d76e52946bd49f5c87e5621cf7dda9e21886 Mon Sep 17 00:00:00 2001
From: "W. Trevor King" <wking@tremily.us>
Date: Fri, 29 Nov 2013 17:48:12 -0800
Subject: [PATCH] README.md: Mention Git flow

Give folks an idea of what's possible.

After editing cheat-sheet.md in my text editor, staging and committing
it was the usual:

  $ git add README.md
  $ git commit --all --verbose
---
 README.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index bbd45fb..d01499a 100644
--- a/README.md
+++ b/README.md
@@ -1,4 +1,7 @@
-Show how project development generally works in [Git][].
+Show how project development generally works in [Git][].  The
+branching outlined here is pretty standard, but [Git flow][] is
+another popular model with a bit more structure.  It's up to you to
+decide what works best for your project.
 
 Markup
 ======
@@ -9,5 +12,6 @@ appropriately.
 
 
 [Git]: http://www.git-scm.com/
+[Git flow]: http://nvie.com/posts/a-successful-git-branching-model/
 [Markdown]: http://daringfireball.net/projects/markdown/
 [GitHub]: https://github.com/github/markup#markups
-- 
2.26.2