| Junio C Hamano | 40f2f8d | 2006-02-07 08:04:39 | [diff] [blame] | 1 | GIT URLS[[URLS]] |
| 2 | ---------------- |
| 3 | |
| 4 | One of the following notations can be used |
| 5 | to name the remote repository: |
| 6 | |
| 7 | =============================================================== |
| 8 | - rsync://host.xz/path/to/repo.git/ |
| 9 | - http://host.xz/path/to/repo.git/ |
| 10 | - https://host.xz/path/to/repo.git/ |
| 11 | - git://host.xz/path/to/repo.git/ |
| 12 | - git://host.xz/~user/path/to/repo.git/ |
| Junio C Hamano | 7ccb9fd | 2006-07-15 01:38:40 | [diff] [blame] | 13 | - ssh://{startsb}user@{endsb}host.xz/path/to/repo.git/ |
| 14 | - ssh://{startsb}user@{endsb}host.xz/~user/path/to/repo.git/ |
| 15 | - ssh://{startsb}user@{endsb}host.xz/~/path/to/repo.git |
| Junio C Hamano | 40f2f8d | 2006-02-07 08:04:39 | [diff] [blame] | 16 | =============================================================== |
| 17 | |
| Junio C Hamano | 7ccb9fd | 2006-07-15 01:38:40 | [diff] [blame] | 18 | SSH is the default transport protocol. You can optionally specify |
| 19 | which user to log-in as, and an alternate, scp-like syntax is also |
| 20 | supported. Both syntaxes support username expansion, |
| Junio C Hamano | 40f2f8d | 2006-02-07 08:04:39 | [diff] [blame] | 21 | as does the native git protocol. The following three are |
| 22 | identical to the last three above, respectively: |
| 23 | |
| 24 | =============================================================== |
| Junio C Hamano | 7ccb9fd | 2006-07-15 01:38:40 | [diff] [blame] | 25 | - {startsb}user@{endsb}host.xz:/path/to/repo.git/ |
| 26 | - {startsb}user@{endsb}host.xz:~user/path/to/repo.git/ |
| 27 | - {startsb}user@{endsb}host.xz:path/to/repo.git |
| Junio C Hamano | 40f2f8d | 2006-02-07 08:04:39 | [diff] [blame] | 28 | =============================================================== |
| 29 | |
| 30 | To sync with a local directory, use: |
| 31 | |
| 32 | =============================================================== |
| 33 | - /path/to/repo.git/ |
| 34 | =============================================================== |
| 35 | |
| 36 | REMOTES |
| 37 | ------- |
| 38 | |
| 39 | In addition to the above, as a short-hand, the name of a |
| 40 | file in `$GIT_DIR/remotes` directory can be given; the |
| 41 | named file should be in the following format: |
| 42 | |
| 43 | URL: one of the above URL format |
| 44 | Push: <refspec> |
| 45 | Pull: <refspec> |
| 46 | |
| 47 | Then such a short-hand is specified in place of |
| 48 | <repository> without <refspec> parameters on the command |
| 49 | line, <refspec> specified on `Push:` lines or `Pull:` |
| 50 | lines are used for `git-push` and `git-fetch`/`git-pull`, |
| Junio C Hamano | 51c2ab0 | 2006-07-09 20:38:54 | [diff] [blame] | 51 | respectively. Multiple `Push:` and `Pull:` lines may |
| Junio C Hamano | 40f2f8d | 2006-02-07 08:04:39 | [diff] [blame] | 52 | be specified for additional branch mappings. |
| 53 | |
| 54 | The name of a file in `$GIT_DIR/branches` directory can be |
| 55 | specified as an older notation short-hand; the named |
| 56 | file should contain a single line, a URL in one of the |
| 57 | above formats, optionally followed by a hash `#` and the |
| 58 | name of remote head (URL fragment notation). |
| 59 | `$GIT_DIR/branches/<remote>` file that stores a <url> |
| 60 | without the fragment is equivalent to have this in the |
| 61 | corresponding file in the `$GIT_DIR/remotes/` directory. |
| 62 | |
| 63 | URL: <url> |
| 64 | Pull: refs/heads/master:<remote> |
| 65 | |
| 66 | while having `<url>#<head>` is equivalent to |
| 67 | |
| 68 | URL: <url> |
| 69 | Pull: refs/heads/<head>:<remote> |
