Bunco Simulator: Changes To How to use Fossil with this repo

Initial version of "How to use Fossil with this repo"



























1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
You can “use” this repo by clicking around these web pages, reading code, wiki pages,&nbsp;etc.

But you can also use Fossil to check out a version-controlled copy of the code. Below are instructions for getting started quickly. The instructions assume you are familiar with <a href="https://fossil-scm.org/index.html/doc/trunk/www/whyusefossil.wiki">the concepts of version control</a>.

<ol>
<li>If you don’t already have it, <a href="http://fossil-scm.org/index.html/uv/download.html">download</a> the Fossil executable and put it on your&nbsp;<code>$PATH</code></li>
<li>Clone this repository:
<pre><code><b>&gt;</b> fossil [https://fossil-scm.org/index.html/help?cmd=clone|clone] -u https://thenotepad.org/repos/bunco bunco.fossil</code></pre></li>
<li>You might as well set autosync to <tt>0</tt> (off) or to <tt>pullonly</tt>. (See below for more info about&nbsp;why):
<pre><code><b>&gt;</b> fossil settings [https://fossil-scm.org/index.html/help?cmd=autosync|autosync] 0</code></pre></li>
<li>“Check out” the latest version of the source code into your current&nbsp;directory:
<pre><code><b>&gt;</b> fossil [https://fossil-scm.org/index.html/help?cmd=open|open] myclone.fossil</code></pre></li>
<li>Fiddle with the source code as you see fit. Read [http://fossil-scm.org/index.html/doc/trunk/www/quickstart.wiki|Fossil Quick Start].</li>
<li>You can also open the web&nbsp;UI for your local copy:
<pre><code><b>&gt;</b> fossil ui</code></pre></li>
<li>To get the latest version of the&nbsp;code:
<pre><code><b>&gt;</b> fossil pull</code></pre></li>
</ol>

<h2>Some tips for Git users</h2>

  *  Fossil has <code>autosync</code> on by default, which means it will sync with the remote repo on every commit. But since you likely won’t have “push” privileges on my repo, it will fail. Turning autosync off will prevent you from having to see it try and fail every time you make a commit.
  *  There is no “staging” step in Fossil. Doing <a href="http://fossil-scm.org/index.html/help?cmd=commit"><code>fossil commit</code></a> immediately commits all changes in all tracked files into the repository. If you need to, you can specify which file or files you want to be included in the&nbsp;commit.
  *  There is no selective “patch committing” in Fossil (i.e., <code>git add -p</code> in Git), reportedly because it facilitates check-ins of untested code. So, if you’re in the habit of making unrelated edits to code…[https://youtu.be/Ow0lr63y4Mw?t=2m7s|stop it!]
  *  There is currently no “pull request” functionality in Fossil; users either have commit privileges or they don’t. This is fine for me since I am not interested in pull requests. If you would like to propose a change you can email me a patch.

























1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25	+ + + + + + + + + + + + + + + + + + + + + + + + +	You can “use” this repo by clicking around these web pages, reading code, wiki pages, etc. But you can also use Fossil to check out a version-controlled copy of the code. Below are instructions for getting started quickly. The instructions assume you are familiar with <a href="https://fossil-scm.org/index.html/doc/trunk/www/whyusefossil.wiki">the concepts of version control</a>. <ol> <li>If you don’t already have it, <a href="http://fossil-scm.org/index.html/uv/download.html">download</a> the Fossil executable and put it on your <code>$PATH</code></li> <li>Clone this repository: <pre><code><b>></b> fossil [https://fossil-scm.org/index.html/help?cmd=clone\|clone] -u https://thenotepad.org/repos/bunco bunco.fossil</code></pre></li> <li>You might as well set autosync to <tt>0</tt> (off) or to <tt>pullonly</tt>. (See below for more info about why): <pre><code><b>></b> fossil settings [https://fossil-scm.org/index.html/help?cmd=autosync\|autosync] 0</code></pre></li> <li>“Check out” the latest version of the source code into your current directory: <pre><code><b>></b> fossil [https://fossil-scm.org/index.html/help?cmd=open\|open] myclone.fossil</code></pre></li> <li>Fiddle with the source code as you see fit. Read [http://fossil-scm.org/index.html/doc/trunk/www/quickstart.wiki\|Fossil Quick Start].</li> <li>You can also open the web UI for your local copy: <pre><code><b>></b> fossil ui</code></pre></li> <li>To get the latest version of the code: <pre><code><b>></b> fossil pull</code></pre></li> </ol> <h2>Some tips for Git users</h2> * Fossil has <code>autosync</code> on by default, which means it will sync with the remote repo on every commit. But since you likely won’t have “push” privileges on my repo, it will fail. Turning autosync off will prevent you from having to see it try and fail every time you make a commit. * There is no “staging” step in Fossil. Doing <a href="http://fossil-scm.org/index.html/help?cmd=commit"><code>fossil commit</code></a> immediately commits all changes in all tracked files into the repository. If you need to, you can specify which file or files you want to be included in the commit. * There is no selective “patch committing” in Fossil (i.e., <code>git add -p</code> in Git), reportedly because it facilitates check-ins of untested code. So, if you’re in the habit of making unrelated edits to code…[https://youtu.be/Ow0lr63y4Mw?t=2m7s\|stop it!] * There is currently no “pull request” functionality in Fossil; users either have commit privileges or they don’t. This is fine for me since I am not interested in pull requests. If you would like to propose a change you can email me a patch.