git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Article on the branch strategy in gitworkflows(7)

From
Raman Gupta <rocketraman@gmail.com>
Date
May 11, 2017, 15:56 UTC
Message-ID
<ba55c352-0cf8-4b89-9d12-819f129a60ee@gmail.com>
In-Reply-To
<92db69d3-ca38-45da-47dc-0fb612a16e8d@gmail.com>

FYI - the article mentioned below has been published @ https://medium.com/@ramangupta/how-the-creators-of-git-do-branches-e6fcc57270fb

Thank you to the two or three people that I know of that took the time to read the draft.

Regards, Raman

On 22/03/17 12:41 PM, Raman Gupta wrote:
Show 34 quoted lines
> Several years ago, I contributed [1] to the gitworkflows(7)
> documentation, because I thought the process by which git.git does
> branching was really interesting.
> 
> Since then, I have found it odd that gitworkflows has mostly remained
> under the radar. Other, in my opinion, lesser flows, have become very
> popular, like GitFlow [2]. I have written an article explaining the
> "why" of gitworkflow in contrast to GitFlow and others:
> 
> https://docs.google.com/document/d/1cGNujRNVzeLV2SXkVlKwai6qJmlVT3LwlOsVYNr0FZo/edit?usp=sharing
> 
> This article is not published yet -- its still a DRAFT and only
> visible via the above URL.
> 
> I'd love to have input on the draft from the experts in this
> community. Feel free to suggest changes and add comments in the
> article via Google Docs.
> 
> Also, some explanatory illustrations to accompany the article would be
> excellent, if anyone feels like contributing. Visuals are not my
> strong suit. I'd love to include something similar to the graphic [3]
> that was a big part of making GitFlow so popular. The article can be
> partially rewritten to match illustrations, if any are contributed.
> 
> [1]
> https://github.com/git/git/commit/382e54312220ac02586a3cbb06b0e4eb7789f043
> 
> [2] http://nvie.com/posts/a-successful-git-branching-model/
> 
> [3] http://nvie.com/img/git-model@2x.png
> 
> Regards,
> Raman Gupta
> 
Previous: Raman Gupta
Message 2 of 2 in “Article on the branch strategy in gitworkflows(7)”
  1. Raman GuptaMar 22, 2017
  2. Raman GuptaMay 11, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.