changed, and finally push to the master branch on the server. The general sequence is something like this: Figure 64. General sequence of events for a simple multiple-developer Git workflow Private Managed or impede the entire team is a huge benefit of Git. The sequence for the workflow you saw here is something like this: Figure 68. Basic sequence of this managed-team workflow Forked Public Project Contributing branch for the patch or patch series you’re planning to contribute, and do your work there. The sequence looks basically like this: $ git clone $ cd project $ git checkout -b featureA ... work

and finally push to the master branch on the server. The general sequence is something like this: 137 Figure 64. General sequence of events for a simple multiple-developer Git workflow Private Managed or impede the entire team is a huge benefit of Git. The sequence for the workflow you saw here is something like this: Figure 68. Basic sequence of this managed-team workflow Forked Public Project Contributing branch for the patch or patch series you’re planning to contribute, and do your work there. The sequence looks basically like this: $ git clone $ cd project $ git checkout -b featureA ... work

changed, and finally push to the master branch on the server. The general sequence is something like this: Figure 64. General sequence of events for a simple multiple-developer Git workflow Private Managed or impede the entire team is a huge benefit of Git. The sequence for the workflow you saw here is something like this: Figure 68. Basic sequence of this managed-team workflow Forked Public Project Contributing branch for the patch or patch series you’re planning to contribute, and do your work there. The sequence looks basically like this: $ git clone $ cd project $ git checkout -b featureA ... work