Changes between Version 1 and Version 2 of RepositoryGuidelines
- Timestamp:
- Feb 26, 2010, 12:06:44 PM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
RepositoryGuidelines
v1 v2 1 = == How to use the Repository on Jupiter ===1 = How to use the Repository on Jupiter = 2 2 3 3 In this page we describe how to get access, the first thing you have to do (clone the repository) and how one should usually proceed to exchange new versions. … … 37 37 Parts of the code that have been implemented and tested successfully have to be broadcast to others. There are two ways to do this. 38 38 39 = ... between users=39 === ... between users === 40 40 41 41 This is easy if your computers reside in the same network (i.e. wiss-stud), just tell your colleague that he should pull one of your branches as this … … 50 50 git remote add <friend> ssh://.../ 51 51 }}} 52 2. Use the remote to fetch all remote branches. 53 {{{ 54 git fetch <friend> 55 }}} 56 3. Merge the obtained remote branch ''<remotebranch>'' with one of yours, here called ''<yours>''. 57 {{{ 58 git checkout <yours> 59 git merge <remotebranch> 60 }}} 61 Note that ''git pull'' performs the fetch and the merge in a single step. 52 62 53 = ... with the jupiter repository=63 === ... with the jupiter repository === 54 64 55 Here, you tell the repository administrator that he should pull one of your branches in the same manner as above. He will check your code and if it is fine, push it onto the jupiter repository. '''Note that you should never ever push yourself branches thereto!''' (except of course you are the administrator :).65 Here, you tell the repository administrator that he should pull one of your branches in the same manner as above. He will check your code and if it is fine, push it onto the jupiter repository. '''Note that you should never ever push branches by yourself thereto! ''' (except of course you are the administrator :). 56 66