Changes between Version 27 and Version 28 of Developer/Git/Committers
- Timestamp:
- 12/03/18 05:44:31 (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Developer/Git/Committers
v27 v28 16 16 = Personal Repository = 17 17 18 Personal repositories keep sthe 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.18 Personal 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. 19 19 20 20 A 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. … … 117 117 You'll still need to delete your local branch if you are done with it. 118 118 119 If 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:119 If 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: 120 120 {{{ 121 121 # git config remote.origin.push test:master … … 137 137 = Pull a Developer's Repo = 138 138 139 The procedures for creating personal repositories ensure sthat 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:139 The 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: 140 140 {{{ 141 141 # git remote add devname git://dispatch.rtems.org/devname/rtems.git