| brians | aede41c | 2013-02-18 04:41:19 +0000 | [diff] [blame^] | 1 | Some us are using git for managing quickly changing code. This file has |
| 2 | directions/notes for setting that up. |
| 3 | |
| 4 | [Cloning] |
| 5 | `git clone \ |
| 6 | ssh://username@robotics.mvla.net/www/https/git/frc971/somebody/2013.git` |
| 7 | where username is your login on the server and somebody is whoever's git |
| 8 | repo you want to clone |
| 9 | |
| 10 | [Adding Other People's Repositories] |
| 11 | `git remote add somebody \ |
| 12 | ssh://username@robotics.mvla.net/www.https/git/frc971/somebody/2013.git` |
| 13 | where username is your login on the server and somebody is another person's |
| 14 | git repository |
| 15 | |
| 16 | [Synchronizing with SVN] |
| 17 | In order to synchronize the git commits with svn, somebody has to get git-svn |
| 18 | set up in their local git repo and then push/pull commits. |
| 19 | To do that, `git svn init https://robotics.mvla.net/svn/frc971/2013/trunk/src` |
| 20 | Then, unless you want git-svn to pull down everything from SVN again, you have |
| 21 | to do `vim .git/refs/remotes/git-svn` (or whatever you name the remote) and |
| 22 | put in the commit ID of the latest commit in the repository that's from SVN. |
| 23 | After doing that (and a `git-svn fetch`), git-svn works like usual. |