Changes between Version 33 and Version 34 of SourceCodeGit


Ignore:
Timestamp:
Feb 8, 2014, 5:31:25 AM (11 years ago)
Author:
Bluefin Tuna
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SourceCodeGit

    v33 v34  
    3737git clone git://boinc.berkeley.edu/boinc-v2.git boinc_repo
    3838}}}
    39 or
     39
     40or, using HTTP:
     41
    4042{{{
    4143git clone http://boinc.berkeley.edu/git/boinc-v2.git boinc_repo
    4244}}}
    4345
    44 This will give you a full copy that you can modify and compile locally, but you will not be able to push changes to the BOINC repository. For write access, see further below.
    45 
    46 If you change to the newly created directory 'boinc_repo', you will see a local copy of the BOINC source code tree.
    47 These are the files corresponding to the 'remote master branch', the bleeding edge of development.
    48 Running `git status` will show that this is actually true:
     46On Windows, you'll need a Git client such as !TortoiseGit (see below).
     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_repo' from the commands above.
     48
     49The '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.
     50
     51Change to the directory 'boinc_repo'. Here you find the files corresponding to the 'remote master branch', the bleeding edge of development.
     52
     53Run `git status` to show that this is actually true:
    4954
    5055{{{
     
    5560}}}
    5661
     62The fully navigable development history of the project can be found in the 'boinc_repo/.git' subdirectory.
     63
    5764You can replace the files on your 'master branch' by files from older branches or older tags using the appropriate git command - without
    58 needing to contact the Git repository server again. This is called 'checking out'. The information to make your local copy of the Git repository a fully navigable development history is tucked away under the '.git' subdirectory.
    59 
    60 On Windows, you'll need a Git client such as !TortoiseGit (see below).
    61 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' from the commands above.
     65needing to contact the Git repository server again as all the history can be found under 'boinc_repo/.git'. This is called 'checking out'.
    6266
    6367== Tags & Branches ==