Fossil SCM
Replaced use of MD blockquotes for command examples with MD code blocks.
Commit
006b61b0e5d43016c4e9779dbbf545cf502f739fe47a4e47f6bbf5a28b8e5ebc
Parent
a974210166464b5…
1 file changed
+7
-7
+7
-7
| --- www/patchcmd.md | ||
| +++ www/patchcmd.md | ||
| @@ -7,11 +7,11 @@ | ||
| 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 | 10 | remote Linux server: |
| 11 | 11 | |
| 12 | -> fossil patch push linuxserver:/path/to/checkout | |
| 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 |
| 16 | 16 | on the remote machine. |
| 17 | 17 | |
| @@ -35,18 +35,18 @@ | ||
| 35 | 35 | PATH on the remote machine. |
| 36 | 36 | |
| 37 | 37 | To check if Fossil is installed correctly on the remote, try a command |
| 38 | 38 | like this: |
| 39 | 39 | |
| 40 | -> `ssh -T remote "fossil version"` | |
| 40 | + ssh -T remote "fossil version" | |
| 41 | 41 | |
| 42 | 42 | If the command above shows a recent version of Fossil, then you should be |
| 43 | 43 | set to go. If you get "fossil not found", or if the version shown is too |
| 44 | 44 | old, put a newer fossil executable on the default PATH. The default PATH |
| 45 | 45 | can be shown using: |
| 46 | 46 | |
| 47 | -> `ssh -T remote 'echo $PATH'` | |
| 47 | + ssh -T remote 'echo $PATH' | |
| 48 | 48 | |
| 49 | 49 | ### Custom PATH Caveat |
| 50 | 50 | |
| 51 | 51 | On Unix-like systems, the init script for the user's login shell |
| 52 | 52 | (e.g. `~/.profile` or `~/.bash_profile`) may be configured to *not do |
| @@ -92,21 +92,21 @@ | ||
| 92 | 92 | argument, then the database is read from that file. If the argument is "-" |
| 93 | 93 | then the database is read from standard input. |
| 94 | 94 | |
| 95 | 95 | Hence the command: |
| 96 | 96 | |
| 97 | -> `fossil patch push remote:projectA` | |
| 97 | + fossil patch push remote:projectA | |
| 98 | 98 | |
| 99 | 99 | Is equivalent to: |
| 100 | 100 | |
| 101 | -> `fossil patch create - | ssh -T remote 'cd projectA;fossil patch apply -'` | |
| 101 | + fossil patch create - | ssh -T remote 'cd projectA;fossil patch apply -' | |
| 102 | 102 | |
| 103 | 103 | Likewise, a command like this: |
| 104 | 104 | |
| 105 | -> `fossil patch pull remote:projB` | |
| 105 | + fossil patch pull remote:projB | |
| 106 | 106 | |
| 107 | 107 | Could be entered like this: |
| 108 | 108 | |
| 109 | -> `ssh -T remote 'cd projB;fossil patch create -' | fossil patch apply -` | |
| 109 | + ssh -T remote 'cd projB;fossil patch create -' | fossil patch apply - | |
| 110 | 110 | |
| 111 | 111 | The "fossil patch view" command just opens the database file and prints |
| 112 | 112 | a summary of its contents on standard output. |
| 113 | 113 |
| --- www/patchcmd.md | |
| +++ www/patchcmd.md | |
| @@ -7,11 +7,11 @@ | |
| 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 |
| 16 | on the remote machine. |
| 17 | |
| @@ -35,18 +35,18 @@ | |
| 35 | PATH on the remote machine. |
| 36 | |
| 37 | To check if Fossil is installed correctly on the remote, try a command |
| 38 | like this: |
| 39 | |
| 40 | > `ssh -T remote "fossil version"` |
| 41 | |
| 42 | If the command above shows a recent version of Fossil, then you should be |
| 43 | set to go. If you get "fossil not found", or if the version shown is too |
| 44 | old, put a newer fossil executable on the default PATH. The default PATH |
| 45 | can be shown using: |
| 46 | |
| 47 | > `ssh -T remote 'echo $PATH'` |
| 48 | |
| 49 | ### Custom PATH Caveat |
| 50 | |
| 51 | On Unix-like systems, the init script for the user's login shell |
| 52 | (e.g. `~/.profile` or `~/.bash_profile`) may be configured to *not do |
| @@ -92,21 +92,21 @@ | |
| 92 | argument, then the database is read from that file. If the argument is "-" |
| 93 | then the database is read from standard input. |
| 94 | |
| 95 | Hence the command: |
| 96 | |
| 97 | > `fossil patch push remote:projectA` |
| 98 | |
| 99 | Is equivalent to: |
| 100 | |
| 101 | > `fossil patch create - | ssh -T remote 'cd projectA;fossil patch apply -'` |
| 102 | |
| 103 | Likewise, a command like this: |
| 104 | |
| 105 | > `fossil patch pull remote:projB` |
| 106 | |
| 107 | Could be entered like this: |
| 108 | |
| 109 | > `ssh -T remote 'cd projB;fossil patch create -' | fossil patch apply -` |
| 110 | |
| 111 | The "fossil patch view" command just opens the database file and prints |
| 112 | a summary of its contents on standard output. |
| 113 |
| --- www/patchcmd.md | |
| +++ www/patchcmd.md | |
| @@ -7,11 +7,11 @@ | |
| 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 |
| 16 | on the remote machine. |
| 17 | |
| @@ -35,18 +35,18 @@ | |
| 35 | PATH on the remote machine. |
| 36 | |
| 37 | To check if Fossil is installed correctly on the remote, try a command |
| 38 | like this: |
| 39 | |
| 40 | ssh -T remote "fossil version" |
| 41 | |
| 42 | If the command above shows a recent version of Fossil, then you should be |
| 43 | set to go. If you get "fossil not found", or if the version shown is too |
| 44 | old, put a newer fossil executable on the default PATH. The default PATH |
| 45 | can be shown using: |
| 46 | |
| 47 | ssh -T remote 'echo $PATH' |
| 48 | |
| 49 | ### Custom PATH Caveat |
| 50 | |
| 51 | On Unix-like systems, the init script for the user's login shell |
| 52 | (e.g. `~/.profile` or `~/.bash_profile`) may be configured to *not do |
| @@ -92,21 +92,21 @@ | |
| 92 | argument, then the database is read from that file. If the argument is "-" |
| 93 | then the database is read from standard input. |
| 94 | |
| 95 | Hence the command: |
| 96 | |
| 97 | fossil patch push remote:projectA |
| 98 | |
| 99 | Is equivalent to: |
| 100 | |
| 101 | fossil patch create - | ssh -T remote 'cd projectA;fossil patch apply -' |
| 102 | |
| 103 | Likewise, a command like this: |
| 104 | |
| 105 | fossil patch pull remote:projB |
| 106 | |
| 107 | Could be entered like this: |
| 108 | |
| 109 | ssh -T remote 'cd projB;fossil patch create -' | fossil patch apply - |
| 110 | |
| 111 | The "fossil patch view" command just opens the database file and prints |
| 112 | a summary of its contents on standard output. |
| 113 |