On Fri, Oct 11, 2013 at 10:39 AM, Josh Elser <[EMAIL PROTECTED]> wrote:

So, comparing to the stock gitflow picture ... The stock gitflow
picture has one 'master' branch that gets tags for the releases, but
not the hotfixes, and one develop branch. Your description reads to me
as an extension of that model to reflect multiple release-history
branches. Do you have the git-flow-ish master/develop distinction for
these, or is it as simple as your next sentence.

Other than the above, we wonder, 'what use is the master branch in the
canonical gitflow picture? :-)'