Changes between Version 27 and Version 28 of Developer/Git/Committers


Ignore:
Timestamp:
Dec 3, 2018, 5:44:31 AM (5 months ago)
Author:
Sal
Comment:

fix typos

Legend:

Unmodified
Added
Removed
Modified
  • Developer/Git/Committers

    v27 v28  
    1616=  Personal Repository  =
    1717
    18 Personal repositories keeps the clutter away from the master repository. A user with a personal repository can make commits, create and delete branches, plus more without interfering with the master repository. Commits to the master repository generate email to the vc@rtems.org list and development type commits by a developer would only add noise and lessen the effectiveness of the commit list.
     18Personal repositories keep the clutter away from the master repository. A user with a personal repository can make commits, create and delete branches, plus more without interfering with the master repository. Commits to the master repository generate email to the vc@rtems.org list and development type commits by a developer would only add noise and lessen the effectiveness of the commit list.
    1919
    2020A committer should maintain a personal clone of the RTEMS repository through which all changes merged into the RTEMS head are sent. The personal repository is also a good place for committers to push branches that contain works in progress. The following instructions show how to setup a personal repository that by default causes commits to go to your private local repository and pushes to go to your publicly visible personal repository. The RTEMS head is configured as a remote repository named 'upstream' to which you can push changes that have been approved for merging into RTEMS.
     
    117117You'll still need to delete your local branch if you are done with it.
    118118
    119 If you are going to work exclusively with one branch for awhile, you might want to configure git to automatically push that branch when you use git push. By default git push will use the local master branch, but you can use the 'test' branch as the source of your changes:
     119If you are going to work exclusively with one branch for a while, you might want to configure git to automatically push that branch when you use git push. By default git push will use the local master branch, but you can use the 'test' branch as the source of your changes:
    120120{{{
    121121# git config remote.origin.push test:master
     
    137137=  Pull a Developer's Repo  =
    138138
    139 The procedures for creating personal repositories ensures that every developer can post branches that anyone else can review. To pull a developer's personal repository into your local RTEMS git clone, just add a new remote repo:
     139The procedures for creating personal repositories ensure that every developer can post branches that anyone else can review. To pull a developer's personal repository into your local RTEMS git clone, just add a new remote repo:
    140140{{{
    141141# git remote add devname git://dispatch.rtems.org/devname/rtems.git