Changes between Version 41 and Version 42 of SourceCodeGit


Ignore:
Timestamp:
Feb 16, 2014, 10:10:58 AM (11 years ago)
Author:
Eric Korpela
Comment:

Naming the boinc head directory to boinc_repo can break autoconf.

Legend:

Unmodified
Added
Removed
Modified

  • SourceCodeGit

    v41 v42  
    3232== Getting a copy of the BOINC source ==
    3333
    34 To clone the BOINC Git repository into a local directory called (for example) 'boinc_repo', run:
    35 
    36 {{{
    37 git clone git://boinc.berkeley.edu/boinc-v2.git boinc_repo
     34To clone the BOINC Git repository into a local directory called (for example) 'boinc', run:
     35
     36{{{
     37git clone git://boinc.berkeley.edu/boinc-v2.git boinc
    3838}}}
    3939
    … …  
    4141
    4242{{{
    43 git clone http://boinc.berkeley.edu/git/boinc-v2.git boinc_repo
     43git clone http://boinc.berkeley.edu/git/boinc-v2.git boinc
    4444}}}
    4545
    4646On Windows, you'll need a Git client such as !TortoiseGit (see below).
    47 Right-click on the parent directory, select 'Git Clone...', and fill in the dialog with one of the above URLs. Don't forget to remove both 'git clone' and 'boinc_repo' from the commands above.
     47Right-click on the parent directory, select 'Git Clone...', and fill in the dialog with one of the above URLs. Don't forget to remove both 'git clone' and 'boinc' from the commands above.
    4848
    4949The 'clone' operation pulls down ~134 MiB of source and gives you a copy that you can modify and compile locally. However, you will not be able to push changes to the BOINC repository. For write access, see further below.
    5050
    51 Change to the directory 'boinc_repo'. Here you find the files corresponding to the HEAD of the 'remote master branch', the bleeding edge of development. The fully navigable development history of the project can be found in the 'boinc_repo/.git' subdirectory.
     51Change to the directory 'boinc'. Here you find the files corresponding to the HEAD of the 'remote master branch', the bleeding edge of development. The fully navigable development history of the project can be found in the 'boinc/.git' subdirectory.
    5252
    5353You can replace the files on your 'master branch' by files from older branches or older tags using the appropriate git command - without
    54 needing to contact the Git repository server again as all the history can be found under 'boinc_repo/.git'. This is called 'checking out'.
     54needing to contact the Git repository server again as all the history can be found under 'boinc/.git'. This is called 'checking out'.
    5555
    5656Run `git status` to see whether there are any changes relative to the HEAD of the 'remote master branch':
    5757
    5858{{{
    59 $ cd boinc_repo
     59$ cd boinc
    6060
    6161$ git status
    … …  
    104104}}}
    105105
    106 inside 'boinc_repo' for a quick text-only history dump:
     106inside 'boinc' for a quick text-only history dump:
    107107
    108108{{{