Changes between Version 24 and Version 25 of Developer/Git/Users


Ignore:
Timestamp:
Dec 2, 2020, 11:30:02 AM (10 months ago)
Author:
rmueller
Comment:

github more information on forking

Legend:

Unmodified
Added
Removed
Modified
  • Developer/Git/Users

    v24 v25  
    4444= Making Changes =
    4545
    46 Git allows you to make changes in the RTEMS source tree and track those changes locally. We recommend you make all your changes in local branches. If you are working on a few different changes or a progression of changes it is best to use a local branch for each change.
     46Git allows you to make changes in the RTEMS source tree and track those changes locally. We recommend you make all your changes in local branches. If you are working on a few different changes or a progression of changes it is best to use a local branch for each change. When working with the RTEMS sources more regularly, it might also be a good idea to fork the repository. This can be done on github as well and is specified in the ''Using a github fork'' section below.
    4747
    4848A branch for each change lets your repo's master branch track the upstream RTEMS's master branch without interacting with any of the changes you are working on. A completed change is emailed to the developer's list for review and this can take time. While this is happening the upstream's master branch may be updated and you may need to rebase your work and test again if you are required to change or update your patch. A local branch isolates a specific change from others and helps you manage the process.
     
    363363
    364364You may prefer to keep your application and development work in a git repository for all the good reasons that come with version control. For public repositories, you may like to try [https://github.com GitHub] or [https://bitbucket.org/ BitBucket]. RTEMS maintains mirrors on GitHub, which can make synchronizing with upstream changes relatively simple. If you need to keep your work private, you can use one of those services with private repositories or manage your own server. The details of setting up a server are outside the scope of this document, but if you have a server with ssh access you should be able to [http://git-scm.com/book/en/Git-on-the-Server-Setting-Up-the-Server find instructions] on how to set up git access. Once you have git configured on the server, adding repositories is a snap.
     365
     366= Using a github fork =
     367
     368A github fork can be created by going to the RTEMS repository you want to work and click the ''Fork'' button at the top right.
     369After that, the fork can be cloned with
     370
     371{{{
     372git clone https://github.com/{github-user-name}/{rtems-repository-name}.git
     373}}}
     374
     375It is recommended to add the main repositories as upstream remotes so changes can be integrated easily
     376
     377{{{
     378git remote add upstream https://github.com/RTEMS/{rtems-repository-name}.git
     379git fetch upstream
     380}}}
     381
     382After that, changes in the upstream master (or any other branch) can be merged like this
     383
     384{{{
     385git merge upstream master
     386}}}
     387
    365388=  Private Servers  =
    366389