Fossil SCM
Tightened up footnote 1 in fossil-v-git to delegate its points more fully to the new mirrorlimitations.md doc.
Commit
0ef227b77cfc20507db56c1084732b6184616c9326c4109ca1019c335c727eca
Parent
c6e8558f2706e76…
1 file changed
+5
-5
+5
-5
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -581,18 +581,18 @@ | ||
| 581 | 581 | <hr/> |
| 582 | 582 | |
| 583 | 583 | <h3>Asides and Digressions</h3> |
| 584 | 584 | |
| 585 | 585 | <i><small><ol> |
| 586 | - <li><p>Git does not include a wiki, a ticket tracker, a forum, or a | |
| 587 | - tech-note feature, so those elements will not transfer when | |
| 588 | - exporting from Fossil to Git. GitHub adds some of these to stock | |
| 586 | + <li><p>[./mirrorlimitations.md|Many | |
| 587 | + things are lost] in making a Git mirror of a Fossil repo due to | |
| 588 | + limitations of Git relative to Fossil. GitHub adds some of these | |
| 589 | + missing features to stock | |
| 589 | 590 | Git, but because they're not part of Git proper, |
| 590 | 591 | [./mirrortogithub.md|exporting a Fossil repository to GitHub] will |
| 591 | 592 | still not include them; Fossil tickets do not become GitHub issues, |
| 592 | - for example. See further discussion in the | |
| 593 | - [./mirrorlimitations.md|Limitations on Git Mirrors] document</p></li> | |
| 593 | + for example. | |
| 594 | 594 | |
| 595 | 595 | <li><p>Both Fossil and Git support |
| 596 | 596 | [https://en.wikipedia.org/wiki/Patch_(Unix)|<tt>patch(1)</tt> |
| 597 | 597 | files], a common way to allow drive-by contributions, but it's a |
| 598 | 598 | lossy contribution path for both systems. Unlike Git PRs and Fossil |
| 599 | 599 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -581,18 +581,18 @@ | |
| 581 | <hr/> |
| 582 | |
| 583 | <h3>Asides and Digressions</h3> |
| 584 | |
| 585 | <i><small><ol> |
| 586 | <li><p>Git does not include a wiki, a ticket tracker, a forum, or a |
| 587 | tech-note feature, so those elements will not transfer when |
| 588 | exporting from Fossil to Git. GitHub adds some of these to stock |
| 589 | Git, but because they're not part of Git proper, |
| 590 | [./mirrortogithub.md|exporting a Fossil repository to GitHub] will |
| 591 | still not include them; Fossil tickets do not become GitHub issues, |
| 592 | for example. See further discussion in the |
| 593 | [./mirrorlimitations.md|Limitations on Git Mirrors] document</p></li> |
| 594 | |
| 595 | <li><p>Both Fossil and Git support |
| 596 | [https://en.wikipedia.org/wiki/Patch_(Unix)|<tt>patch(1)</tt> |
| 597 | files], a common way to allow drive-by contributions, but it's a |
| 598 | lossy contribution path for both systems. Unlike Git PRs and Fossil |
| 599 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -581,18 +581,18 @@ | |
| 581 | <hr/> |
| 582 | |
| 583 | <h3>Asides and Digressions</h3> |
| 584 | |
| 585 | <i><small><ol> |
| 586 | <li><p>[./mirrorlimitations.md|Many |
| 587 | things are lost] in making a Git mirror of a Fossil repo due to |
| 588 | limitations of Git relative to Fossil. GitHub adds some of these |
| 589 | missing features to stock |
| 590 | Git, but because they're not part of Git proper, |
| 591 | [./mirrortogithub.md|exporting a Fossil repository to GitHub] will |
| 592 | still not include them; Fossil tickets do not become GitHub issues, |
| 593 | for example. |
| 594 | |
| 595 | <li><p>Both Fossil and Git support |
| 596 | [https://en.wikipedia.org/wiki/Patch_(Unix)|<tt>patch(1)</tt> |
| 597 | files], a common way to allow drive-by contributions, but it's a |
| 598 | lossy contribution path for both systems. Unlike Git PRs and Fossil |
| 599 |