Changes between Version 26 and Version 27 of Developer/Git


Ignore:
Timestamp:
Feb 2, 2012, 3:02:04 AM (8 years ago)
Author:
Gedare
Comment:

/* GIT Access for contributors */

Legend:

Unmodified
Added
Removed
Modified
  • Developer/Git

    v26 v27  
    229229TODO: Some guidelines for anyone who wishes to contribute to rtems... Patches? Pull Requests?...
    230230
    231 The preferred workflow for making changes to RTEMS is to push patches to a committer's personal repository in public view and then merge changes from there.
     231The preferred workflow for making changes to RTEMS is to push patches to a committer's personal repository in public view and then merge changes from there. For working on enhancements or bug fixes committers are encouraged to push to branches on their personal repositories and to merge into the main RTEMS repository from their personal repository. Personal branches should not be pushed to the RTEMS repository.
    232232=  SSH Access  =
    233233
     
    235235=  Personal Repository  =
    236236
    237 Each committer should maintain a personal clone of the RTEMS repository to which all changes meant to be merged into the RTEMS head are sent. 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.
    238 
    239 Branches aren't automatically pushed until you tell git to do the initial push after which the branch is pushed automatically. In order to keep code private just put it on a branch and do not push the branch.
     237Each committer should maintain a personal clone of the RTEMS repository through which all changes meant to be 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.
     238
     239Branches aren't automatically pushed until you tell git to do the initial push after which the branch is pushed automatically. In order to keep code private just put it on a branch in your local clone and do not push the branch.
    240240=  Create a personal repository  =
    241241