How to use this repo
You can “use” this repo by clicking around and reading code, wiki pages, etc.
But for those who have an account with the right permissions, it can also be used to check out a version-controlled copy of the code.
I’m not yet giving out such accounts, not until the whole project is live. But, for the curious, this is how it would work if you had one:
- If you don’t already have it, download the Fossil executable and put it on your
- Clone this repository:
> fossil clone -u https://user:email@example.com/cgi-bin/yarncode yarn.fossil
- You might as well set autosync to 0 (off) or to pullonly. (See below for more info about why):
> fossil settings autosync 0
- “Check out” the latest version of the source code into your current directory:
> fossil open myclone.fossil
- Fiddle with the source code as you see fit. Read Fossil Quick Start.
- You can also open your own local copy of the web UI:
> fossil ui
- To get the latest version of the code:
> fossil pull
Some tips for Git users
- If you’re wondering why I’m using Fossil instead of Git, read Why Fossil?
- Fossil has
autosyncon 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
fossil commitimmediately 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.,
git add -pin Git), reportedly because it facilitates check-ins of untested code. So, if you’re in the habit of making unrelated edits to code…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.