Show More
@@ -2424,19 +2424,22 b' def pull(ui, repo, source="default", **o' | |||
|
2424 | 2424 | def push(ui, repo, dest=None, **opts): |
|
2425 | 2425 | """push changes to the specified destination |
|
2426 | 2426 | |
|
2427 |
Push changes from the local repository to the specified |
|
|
2428 | ||
|
2429 | This is the symmetrical operation for pull. It moves changes from | |
|
2430 | the current repository to a different one. If the destination is | |
|
2431 | local this is identical to a pull in that directory from the | |
|
2432 | current one. | |
|
2433 | ||
|
2434 | By default, push will refuse to run if it detects the result would | |
|
2435 | increase the number of remote heads. This generally indicates the | |
|
2436 | user forgot to pull and merge before pushing. | |
|
2437 | ||
|
2438 | If -r/--rev is used, the named revision and all its ancestors will | |
|
2439 | be pushed to the remote repository. | |
|
2427 | Push changesets from the local repository to the specified | |
|
2428 | destination. | |
|
2429 | ||
|
2430 | This operation is symmetrical to pull: it is identical to a pull | |
|
2431 | in the destination repository from the current one. | |
|
2432 | ||
|
2433 | By default, push will not allow creation of new heads at the | |
|
2434 | destination, since multiple heads would make it unclear which head | |
|
2435 | to use. In this situation, it is recommended to pull and merge | |
|
2436 | before pushing. | |
|
2437 | ||
|
2438 | Use -f/--force to override the default behavior and push all | |
|
2439 | changesets on all branches. | |
|
2440 | ||
|
2441 | If -r/--rev is used, the specified revision and all its ancestors | |
|
2442 | will be pushed to the remote repository. | |
|
2440 | 2443 | |
|
2441 | 2444 | Please see 'hg help urls' for important details about ``ssh://`` |
|
2442 | 2445 | URLs. If DESTINATION is omitted, a default path will be used. |
General Comments 0
You need to be logged in to leave comments.
Login now