Fossil SCM
Minor fixes to the cleanup of the "patchcmd.md" document.
Commit
990019346ea1588d73757cabd067ce11bbe547e94bf98d327fec17e711ae0907
Parent
e0d61109e114511…
1 file changed
+6
-2
+6
-2
| --- www/patchcmd.md | ||
| +++ www/patchcmd.md | ||
| @@ -5,11 +5,11 @@ | ||
| 5 | 5 | those changes to other machines. |
| 6 | 6 | |
| 7 | 7 | For example, if you are working on a Windows desktop and you want to |
| 8 | 8 | test your changes on a Linux server before you commit, you can use the |
| 9 | 9 | "fossil patch push" command to make a copy of all your changes on the |
| 10 | -remote Linux server, where they can be tested. | |
| 10 | +remote Linux server: | |
| 11 | 11 | |
| 12 | 12 | > fossil patch push linuxserver:/path/to/checkout |
| 13 | 13 | |
| 14 | 14 | In the previous "linuxserver" is the name of the remote machine and |
| 15 | 15 | "/path/to/checkout" is an existing checkout directory for the same project |
| @@ -21,10 +21,14 @@ | ||
| 21 | 21 | steps apart as follows: |
| 22 | 22 | |
| 23 | 23 | 1. On the local machine: `fossil patch create mypatch.patch` |
| 24 | 24 | 2. Move "mypatch.patch" to the remote machine. |
| 25 | 25 | 3. On the remote machine: `fossil patch apply mypatch.patch` |
| 26 | + | |
| 27 | +Step 2 can be accomplished by a variety of means including | |
| 28 | +posting the mypatch.patch file on [chat](./chat.md) or sending | |
| 29 | +it as an email attachment. | |
| 26 | 30 | |
| 27 | 31 | ## Setup |
| 28 | 32 | |
| 29 | 33 | The "fossil push" and "fossil pull" commands will only work if you have |
| 30 | 34 | "ssh" available on the local machine and if "fossil" is on the default |
| @@ -62,13 +66,13 @@ | ||
| 62 | 66 | |
| 63 | 67 | > `fossil patch create - | ssh -T remote 'cd projectA;fossil patch apply -'` |
| 64 | 68 | |
| 65 | 69 | Likewise, a command like this: |
| 66 | 70 | |
| 67 | -> `fossil patch pull remote:projB | |
| 71 | +> `fossil patch pull remote:projB` | |
| 68 | 72 | |
| 69 | 73 | Could be entered like this: |
| 70 | 74 | |
| 71 | 75 | > `ssh -T remote 'cd projB;fossil patch create -' | fossil patch apply -` |
| 72 | 76 | |
| 73 | 77 | The "fossil patch view" command just opens the database file and prints |
| 74 | 78 | a summary of its contents on standard output. |
| 75 | 79 |
| --- www/patchcmd.md | |
| +++ www/patchcmd.md | |
| @@ -5,11 +5,11 @@ | |
| 5 | those changes to other machines. |
| 6 | |
| 7 | For example, if you are working on a Windows desktop and you want to |
| 8 | test your changes on a Linux server before you commit, you can use the |
| 9 | "fossil patch push" command to make a copy of all your changes on the |
| 10 | remote Linux server, where they can be tested. |
| 11 | |
| 12 | > fossil patch push linuxserver:/path/to/checkout |
| 13 | |
| 14 | In the previous "linuxserver" is the name of the remote machine and |
| 15 | "/path/to/checkout" is an existing checkout directory for the same project |
| @@ -21,10 +21,14 @@ | |
| 21 | steps apart as follows: |
| 22 | |
| 23 | 1. On the local machine: `fossil patch create mypatch.patch` |
| 24 | 2. Move "mypatch.patch" to the remote machine. |
| 25 | 3. On the remote machine: `fossil patch apply mypatch.patch` |
| 26 | |
| 27 | ## Setup |
| 28 | |
| 29 | The "fossil push" and "fossil pull" commands will only work if you have |
| 30 | "ssh" available on the local machine and if "fossil" is on the default |
| @@ -62,13 +66,13 @@ | |
| 62 | |
| 63 | > `fossil patch create - | ssh -T remote 'cd projectA;fossil patch apply -'` |
| 64 | |
| 65 | Likewise, a command like this: |
| 66 | |
| 67 | > `fossil patch pull remote:projB |
| 68 | |
| 69 | Could be entered like this: |
| 70 | |
| 71 | > `ssh -T remote 'cd projB;fossil patch create -' | fossil patch apply -` |
| 72 | |
| 73 | The "fossil patch view" command just opens the database file and prints |
| 74 | a summary of its contents on standard output. |
| 75 |
| --- www/patchcmd.md | |
| +++ www/patchcmd.md | |
| @@ -5,11 +5,11 @@ | |
| 5 | those changes to other machines. |
| 6 | |
| 7 | For example, if you are working on a Windows desktop and you want to |
| 8 | test your changes on a Linux server before you commit, you can use the |
| 9 | "fossil patch push" command to make a copy of all your changes on the |
| 10 | remote Linux server: |
| 11 | |
| 12 | > fossil patch push linuxserver:/path/to/checkout |
| 13 | |
| 14 | In the previous "linuxserver" is the name of the remote machine and |
| 15 | "/path/to/checkout" is an existing checkout directory for the same project |
| @@ -21,10 +21,14 @@ | |
| 21 | steps apart as follows: |
| 22 | |
| 23 | 1. On the local machine: `fossil patch create mypatch.patch` |
| 24 | 2. Move "mypatch.patch" to the remote machine. |
| 25 | 3. On the remote machine: `fossil patch apply mypatch.patch` |
| 26 | |
| 27 | Step 2 can be accomplished by a variety of means including |
| 28 | posting the mypatch.patch file on [chat](./chat.md) or sending |
| 29 | it as an email attachment. |
| 30 | |
| 31 | ## Setup |
| 32 | |
| 33 | The "fossil push" and "fossil pull" commands will only work if you have |
| 34 | "ssh" available on the local machine and if "fossil" is on the default |
| @@ -62,13 +66,13 @@ | |
| 66 | |
| 67 | > `fossil patch create - | ssh -T remote 'cd projectA;fossil patch apply -'` |
| 68 | |
| 69 | Likewise, a command like this: |
| 70 | |
| 71 | > `fossil patch pull remote:projB` |
| 72 | |
| 73 | Could be entered like this: |
| 74 | |
| 75 | > `ssh -T remote 'cd projB;fossil patch create -' | fossil patch apply -` |
| 76 | |
| 77 | The "fossil patch view" command just opens the database file and prints |
| 78 | a summary of its contents on standard output. |
| 79 |