README.md: Mention Git flow master
authorW. Trevor King <wking@tremily.us>
Sat, 30 Nov 2013 01:48:12 +0000 (17:48 -0800)
committerW. Trevor King <wking@tremily.us>
Sat, 30 Nov 2013 01:48:12 +0000 (17:48 -0800)
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

index bbd45fbf047a42e9ebd6005debf1e486644dfce9..d01499a7c3abb0c9d7eb230e635f8849f9d30397 100644 (file)
--- 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
 ======
 
 Markup
 ======
@@ -9,5 +12,6 @@ appropriately.
 
 
 [Git]: http://www.git-scm.com/
 
 
 [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
 [Markdown]: http://daringfireball.net/projects/markdown/
 [GitHub]: https://github.com/github/markup#markups