X-Git-Url: https://git.phdru.name/?a=blobdiff_plain;f=pep-git.txt;h=db703eb15e3f69c2e1ee31bfc9b72b000b5c95ed;hb=0f336f194e546c229b2ff7cbac92910a4bb749f6;hp=a10477f4f238eafaca3c0db6085db767fe775d47;hpb=af80a56f3bc5f3a777d6431bba02949d55808879;p=git-wiki.git diff --git a/pep-git.txt b/pep-git.txt index a10477f..db703eb 100644 --- a/pep-git.txt +++ b/pep-git.txt @@ -43,7 +43,7 @@ Git Tutorial: `part 1 `Git User's manual `_. `Everyday GIT With 20 Commands Or So -`_. +`_. `Git workflows `_. @@ -628,6 +628,33 @@ Git has a builtin merge strategy for what Python core developers call $ git merge -s ours v1 # null-merge v1 into master +Branching models +================ + +Git doesn't assume any particular development model regarding +branching and merging. Some projects prefer to graduate patches from +the oldest branch to the newest, some prefer to cherry-pick commits +backwards, some use squashing (combining a number of commits into +one). Anything is possible. + +There are a few examples to start with. `git help workflows +`_ +describes how the very git authors develop git. + +ProGit book has a few chapters devoted to branch management in +different projects: `Git Branching - Branching Workflows +`_ and +`Distributed Git - Contributing to a Project +`_. + +There is also a well-known article `A successful Git branching model +`_ by Vincent +Driessen. It recommends a set of very detailed rules on creating and +managing mainline, topic and bugfix branches. To support the model the +author implemented `git flow `_ +extension. + + Advanced configuration ======================