Git workflow: whats the difference from SVN? -

Git workflow: whats the difference from SVN? -

i have read these 2 papers git workflow:

http://nvie.com/posts/a-successful-git-branching-model/ https://www.atlassian.com/git/tutorials/comparing-workflows/

as far understand, model simple:

we have develop branch (ex-trunk), we create feature branches merged develop when ready, we create release branch when features implemented , merge release branches master in 1 commit when ready (and develop integrity). finally tag master branch.

well, question is:

is there important differences model in other examples of gitworkflow? if no, differences between model , standart svn development? why phone call "gitworkflow" - cannot see difference standart svn development scheme. can same svn. , :)

so way called gitworkflow, or may there points have missed?

as far understand, model simple

your understanding massively wrong

gitflow rather complex workflow gitflow assumes set of families of purpose-oriented branches (feature*, hotfix*, release*) lot of predefined rules order , direction of cross-branch merges

what differences between model , standart svn development?

"standard" svn development doesn't exist - there @ to the lowest degree 2 widely-used svn-workflows ("stable trunk" vs "unstable trunk|no branches") any svn-workflow assumes few merges, possible (svn-merges still headache), gitflow built around intensive merging between special-purpose branches

git svn version-control