Re: git branch diagram

From: Matt Graham <mdg149@gmail.com>
Date: Apr 18, 2008, 13:07 UTC
Message-ID: <1c5969370804180607q675eb528na431ecdce99c49fd@mail.gmail.com>
In-Reply-To: <911589C97062424796D53B625CEC0025E460C3@USCOBRMFA-SE-70.northamerica.cexp.com>

Full disclosure: I'm a git newbie.

On Thu, Apr 17, 2008 at 1:00 PM,  <Patrick.Higgins@cexp.com> wrote:

> I am trying to get my employer to start using git and have found the distributed model and git's branching to be one of the hardest parts to explain and understand. I put together the attached diagram (done with graphviz so some things are not in the most logical place) to help explain things to my coworkers.
>

A worthy goal. It seems like a good corporate work flow for git is either yet to be devised or yet to be documented.

>  In my diagram, I am assuming that most developers work in master, and make branches for their own long-lived projects and experimental things.
>
>  Does my diagram make sense? Are there any suggestions or corrections?

It feels more complicated than it needs to be. My reaction is that there should be a simpler way to represent it.

In the dev repos, do the remote branches and local branches have to be in separate boxes? It seems these could be put into a single box.

It's not clear who's doing the pulls into the project repository or who is doing the integration. My expectation would be that pushes would be involved at some point, is it not necessary?

matt