| 120 | | The -m option has the same meaning as the svn commit command. The -a option "bypasses" the index, and tells git to commit all your changes. By default (without the "-a"), git only commits the changes you explicitly told him about with the add command (TODO: ref to git-specific workflows). |
| | 120 | The -m option has the same meaning as the svn commit command. By default (without the "-a"), git only commits the changes you explicitly told him about with the add command (TODO: ref to git-specific workflows). Although extremely useful, it can be a bit confusing at first when you come from a svn background, hence the -a option. |
| | 121 | |
| | 122 | A big difference of git compared to svn which cannot be skipped even at this level: git clone gives you a working tree (a snapshot of the sources at one revision) AND the repository with the full history. It means in particular that committing a change will NOT propagate it to the original repository you cloned from. For this, you need to use push: |
| | 123 | |
| | 124 | {{{ |
| | 125 | git push git.scipy.org/git/numpy |
| | 126 | }}} |
| | 127 | |
| | 128 | TODO: handling of remote locations. |
| | 129 | |
