Fossil

Check-in [0ef227b7]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Tightened up footnote 1 in fossil-v-git to delegate its points more fully to the new mirrorlimitations.md doc.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: 0ef227b77cfc20507db56c1084732b6184616c9326c4109ca1019c335c727eca
User & Date: wyoung 2019-08-07 01:00:06
Context
2019-08-07
01:45
Added footnote 2 to the fossil-v-git doc, which explains that not "everything" on fossil-scm.org is in the main Fossil self-hosting repo, and links to info explaining the details. check-in: d23a8453 user: wyoung tags: trunk
01:00
Tightened up footnote 1 in fossil-v-git to delegate its points more fully to the new mirrorlimitations.md doc. check-in: 0ef227b7 user: wyoung tags: trunk
00:53
Updated the "A Pure SHA3 Future" section of www/hashpolicy.wiki to track the recent decision to make "sha3" mode the default in Fossil 2.10. check-in: c6e8558f user: wyoung tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to www/fossil-v-git.wiki.

579
580
581
582
583
584
585
586
587
588

589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
   a complete record and on sharing everything between all developers.

<hr/>

<h3>Asides and Digressions</h3>

<i><small><ol>
    <li><p>Git does not include a wiki, a ticket tracker, a forum, or a
    tech-note feature, so those elements will not transfer when
    exporting from Fossil to Git. GitHub adds some of these to stock

    Git, but because they're not part of Git proper,
    [./mirrortogithub.md|exporting a Fossil repository to GitHub] will
    still not include them; Fossil tickets do not become GitHub issues,
    for example.  See further discussion in the
    [./mirrorlimitations.md|Limitations on Git Mirrors] document</p></li>

    <li><p>Both Fossil and Git support
    [https://en.wikipedia.org/wiki/Patch_(Unix)|<tt>patch(1)</tt>
    files], a common way to allow drive-by contributions, but it's a
    lossy contribution path for both systems. Unlike Git PRs and Fossil
    bundles, patch files collapse mulitple checkins together, they don't
    include check-in comments, and they cannot encode changes made above
    the individual file content layer: you lose branching decisisions,
    tag changes, file renames, and more when using patch files.</p></li>
</ol></i></small>







|
|
|
>



|
<










579
580
581
582
583
584
585
586
587
588
589
590
591
592
593

594
595
596
597
598
599
600
601
602
603
   a complete record and on sharing everything between all developers.

<hr/>

<h3>Asides and Digressions</h3>

<i><small><ol>
    <li><p>[./mirrorlimitations.md|Many
    things are lost] in making a Git mirror of a Fossil repo due to
    limitations of Git relative to Fossil. GitHub adds some of these
    missing features to stock
    Git, but because they're not part of Git proper,
    [./mirrortogithub.md|exporting a Fossil repository to GitHub] will
    still not include them; Fossil tickets do not become GitHub issues,
    for example.


    <li><p>Both Fossil and Git support
    [https://en.wikipedia.org/wiki/Patch_(Unix)|<tt>patch(1)</tt>
    files], a common way to allow drive-by contributions, but it's a
    lossy contribution path for both systems. Unlike Git PRs and Fossil
    bundles, patch files collapse mulitple checkins together, they don't
    include check-in comments, and they cannot encode changes made above
    the individual file content layer: you lose branching decisisions,
    tag changes, file renames, and more when using patch files.</p></li>
</ol></i></small>