597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
|
for example.
<li><p>The <tt>fossil-scm.org</tt> web site is actually hosted in
several parts, so that it is not strictly true that "everything" on
it is in the self-hosting Fossil project repo. The web forum is
hosted as a separate Fossil repo from the code for administration
reasons, and the Download page content isn't normally sync'd with a
"<tt>fossil clone</tt>" command due to [./aboutdownload.wiki|the way
it's implemented].
<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
|
|
|
>
|
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
|
for example.
<li><p>The <tt>fossil-scm.org</tt> web site is actually hosted in
several parts, so that it is not strictly true that "everything" on
it is in the self-hosting Fossil project repo. The web forum is
hosted as a separate Fossil repo from the code for administration
reasons, and the Download page content isn't normally sync'd with a
"<tt>fossil clone</tt>" command unless you add the "-u" option.
See the description of [./aboutdownload.wiki|how download is implemented]
for details.
<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
|