Fossil SCM
Remove uncommonly used commands from the set of "common" commands in the "fossil help" listing.
Commit
29313518937ca912e0fa115a65d32fdd36cc3cfc83712f660b8fd51b4818ece3
Parent
71c298f3ea42391…
4 files changed
+1
-1
+1
-1
+2
-2
+3
-2
+1
-1
| --- src/alerts.c | ||
| +++ src/alerts.c | ||
| @@ -922,11 +922,11 @@ | ||
| 922 | 922 | ** designated host and port and all times. |
| 923 | 923 | */ |
| 924 | 924 | |
| 925 | 925 | |
| 926 | 926 | /* |
| 927 | -** COMMAND: alerts | |
| 927 | +** COMMAND: alerts* | |
| 928 | 928 | ** |
| 929 | 929 | ** Usage: %fossil alerts SUBCOMMAND ARGS... |
| 930 | 930 | ** |
| 931 | 931 | ** Subcommands: |
| 932 | 932 | ** |
| 933 | 933 |
| --- src/alerts.c | |
| +++ src/alerts.c | |
| @@ -922,11 +922,11 @@ | |
| 922 | ** designated host and port and all times. |
| 923 | */ |
| 924 | |
| 925 | |
| 926 | /* |
| 927 | ** COMMAND: alerts |
| 928 | ** |
| 929 | ** Usage: %fossil alerts SUBCOMMAND ARGS... |
| 930 | ** |
| 931 | ** Subcommands: |
| 932 | ** |
| 933 |
| --- src/alerts.c | |
| +++ src/alerts.c | |
| @@ -922,11 +922,11 @@ | |
| 922 | ** designated host and port and all times. |
| 923 | */ |
| 924 | |
| 925 | |
| 926 | /* |
| 927 | ** COMMAND: alerts* |
| 928 | ** |
| 929 | ** Usage: %fossil alerts SUBCOMMAND ARGS... |
| 930 | ** |
| 931 | ** Subcommands: |
| 932 | ** |
| 933 |
+1
-1
| --- src/backoffice.c | ||
| +++ src/backoffice.c | ||
| @@ -524,11 +524,11 @@ | ||
| 524 | 524 | alert_backoffice(0); |
| 525 | 525 | smtp_cleanup(); |
| 526 | 526 | } |
| 527 | 527 | |
| 528 | 528 | /* |
| 529 | -** COMMAND: backoffice | |
| 529 | +** COMMAND: backoffice* | |
| 530 | 530 | ** |
| 531 | 531 | ** Usage: backoffice [-R repository] |
| 532 | 532 | ** |
| 533 | 533 | ** Run backoffice processing. This might be done by a cron job or |
| 534 | 534 | ** similar to make sure backoffice processing happens periodically. |
| 535 | 535 |
| --- src/backoffice.c | |
| +++ src/backoffice.c | |
| @@ -524,11 +524,11 @@ | |
| 524 | alert_backoffice(0); |
| 525 | smtp_cleanup(); |
| 526 | } |
| 527 | |
| 528 | /* |
| 529 | ** COMMAND: backoffice |
| 530 | ** |
| 531 | ** Usage: backoffice [-R repository] |
| 532 | ** |
| 533 | ** Run backoffice processing. This might be done by a cron job or |
| 534 | ** similar to make sure backoffice processing happens periodically. |
| 535 |
| --- src/backoffice.c | |
| +++ src/backoffice.c | |
| @@ -524,11 +524,11 @@ | |
| 524 | alert_backoffice(0); |
| 525 | smtp_cleanup(); |
| 526 | } |
| 527 | |
| 528 | /* |
| 529 | ** COMMAND: backoffice* |
| 530 | ** |
| 531 | ** Usage: backoffice [-R repository] |
| 532 | ** |
| 533 | ** Run backoffice processing. This might be done by a cron job or |
| 534 | ** similar to make sure backoffice processing happens periodically. |
| 535 |
+2
-2
| --- src/smtp.c | ||
| +++ src/smtp.c | ||
| @@ -1310,11 +1310,11 @@ | ||
| 1310 | 1310 | } |
| 1311 | 1311 | } |
| 1312 | 1312 | |
| 1313 | 1313 | |
| 1314 | 1314 | /* |
| 1315 | -** COMMAND: smtpd | |
| 1315 | +** COMMAND: smtpd* | |
| 1316 | 1316 | ** |
| 1317 | 1317 | ** Usage: %fossil smtpd [OPTIONS] REPOSITORY |
| 1318 | 1318 | ** |
| 1319 | 1319 | ** Begin a SMTP conversation with a client using stdin/stdout. The |
| 1320 | 1320 | ** received email is stored in REPOSITORY. |
| @@ -1457,11 +1457,11 @@ | ||
| 1457 | 1457 | static int pop3_login(const char *zUser, char *zPass){ |
| 1458 | 1458 | return login_search_uid(&zUser, zPass) != 0; |
| 1459 | 1459 | } |
| 1460 | 1460 | |
| 1461 | 1461 | /* |
| 1462 | -** COMMAND: pop3d | |
| 1462 | +** COMMAND: pop3d* | |
| 1463 | 1463 | ** |
| 1464 | 1464 | ** Usage: %fossil pop3d [OPTIONS] REPOSITORY |
| 1465 | 1465 | ** |
| 1466 | 1466 | ** Begin a POP3 conversation with a client using stdin/stdout using |
| 1467 | 1467 | ** the mailboxes stored in REPOSITORY. |
| 1468 | 1468 |
| --- src/smtp.c | |
| +++ src/smtp.c | |
| @@ -1310,11 +1310,11 @@ | |
| 1310 | } |
| 1311 | } |
| 1312 | |
| 1313 | |
| 1314 | /* |
| 1315 | ** COMMAND: smtpd |
| 1316 | ** |
| 1317 | ** Usage: %fossil smtpd [OPTIONS] REPOSITORY |
| 1318 | ** |
| 1319 | ** Begin a SMTP conversation with a client using stdin/stdout. The |
| 1320 | ** received email is stored in REPOSITORY. |
| @@ -1457,11 +1457,11 @@ | |
| 1457 | static int pop3_login(const char *zUser, char *zPass){ |
| 1458 | return login_search_uid(&zUser, zPass) != 0; |
| 1459 | } |
| 1460 | |
| 1461 | /* |
| 1462 | ** COMMAND: pop3d |
| 1463 | ** |
| 1464 | ** Usage: %fossil pop3d [OPTIONS] REPOSITORY |
| 1465 | ** |
| 1466 | ** Begin a POP3 conversation with a client using stdin/stdout using |
| 1467 | ** the mailboxes stored in REPOSITORY. |
| 1468 |
| --- src/smtp.c | |
| +++ src/smtp.c | |
| @@ -1310,11 +1310,11 @@ | |
| 1310 | } |
| 1311 | } |
| 1312 | |
| 1313 | |
| 1314 | /* |
| 1315 | ** COMMAND: smtpd* |
| 1316 | ** |
| 1317 | ** Usage: %fossil smtpd [OPTIONS] REPOSITORY |
| 1318 | ** |
| 1319 | ** Begin a SMTP conversation with a client using stdin/stdout. The |
| 1320 | ** received email is stored in REPOSITORY. |
| @@ -1457,11 +1457,11 @@ | |
| 1457 | static int pop3_login(const char *zUser, char *zPass){ |
| 1458 | return login_search_uid(&zUser, zPass) != 0; |
| 1459 | } |
| 1460 | |
| 1461 | /* |
| 1462 | ** COMMAND: pop3d* |
| 1463 | ** |
| 1464 | ** Usage: %fossil pop3d [OPTIONS] REPOSITORY |
| 1465 | ** |
| 1466 | ** Begin a POP3 conversation with a client using stdin/stdout using |
| 1467 | ** the mailboxes stored in REPOSITORY. |
| 1468 |
+3
-2
| --- www/blockchain.md | ||
| +++ www/blockchain.md | ||
| @@ -16,15 +16,16 @@ | ||
| 16 | 16 | a timestamp, and other tranactional data. The repository grows by |
| 17 | 17 | add new manifests onto the list. |
| 18 | 18 | |
| 19 | 19 | Some people have come to associate blockchain with cryptocurrency, however, |
| 20 | 20 | and since Fossil has nothing to do with cryptocurrency, the claim that |
| 21 | -Fossil is build around blockchain results in confusion. The key thing | |
| 21 | +Fossil is build around blockchain is met with skepticism. The key thing | |
| 22 | 22 | to note here is that cryptocurrency implementations like BitCoin are |
| 23 | 23 | built around blockchain, but they are not synonymous with blockchain. |
| 24 | 24 | Blockchain is a much broader concept. Blockchain is a mechanism for |
| 25 | -constructed a distributed ledger of transactions. You can use a distributed | |
| 25 | +constructed a distributed ledger of transactions. | |
| 26 | +Yes, you can use a distributed | |
| 26 | 27 | ledger to implement a cryptocurrency, but you can also use a distributed |
| 27 | 28 | ledger to implement a version control system, and probably many other kinds |
| 28 | 29 | of applications as well. Blockchain is a much broader idea than |
| 29 | 30 | cryptocurrency. |
| 30 | 31 | |
| 31 | 32 |
| --- www/blockchain.md | |
| +++ www/blockchain.md | |
| @@ -16,15 +16,16 @@ | |
| 16 | a timestamp, and other tranactional data. The repository grows by |
| 17 | add new manifests onto the list. |
| 18 | |
| 19 | Some people have come to associate blockchain with cryptocurrency, however, |
| 20 | and since Fossil has nothing to do with cryptocurrency, the claim that |
| 21 | Fossil is build around blockchain results in confusion. The key thing |
| 22 | to note here is that cryptocurrency implementations like BitCoin are |
| 23 | built around blockchain, but they are not synonymous with blockchain. |
| 24 | Blockchain is a much broader concept. Blockchain is a mechanism for |
| 25 | constructed a distributed ledger of transactions. You can use a distributed |
| 26 | ledger to implement a cryptocurrency, but you can also use a distributed |
| 27 | ledger to implement a version control system, and probably many other kinds |
| 28 | of applications as well. Blockchain is a much broader idea than |
| 29 | cryptocurrency. |
| 30 | |
| 31 |
| --- www/blockchain.md | |
| +++ www/blockchain.md | |
| @@ -16,15 +16,16 @@ | |
| 16 | a timestamp, and other tranactional data. The repository grows by |
| 17 | add new manifests onto the list. |
| 18 | |
| 19 | Some people have come to associate blockchain with cryptocurrency, however, |
| 20 | and since Fossil has nothing to do with cryptocurrency, the claim that |
| 21 | Fossil is build around blockchain is met with skepticism. The key thing |
| 22 | to note here is that cryptocurrency implementations like BitCoin are |
| 23 | built around blockchain, but they are not synonymous with blockchain. |
| 24 | Blockchain is a much broader concept. Blockchain is a mechanism for |
| 25 | constructed a distributed ledger of transactions. |
| 26 | Yes, you can use a distributed |
| 27 | ledger to implement a cryptocurrency, but you can also use a distributed |
| 28 | ledger to implement a version control system, and probably many other kinds |
| 29 | of applications as well. Blockchain is a much broader idea than |
| 30 | cryptocurrency. |
| 31 | |
| 32 |