GIT.BI6.US
Hosted Repositories
This is the list of public GIT repositories hosted on GIT.BI6.US.
| HTTPS://GIT.BI6.US/TEST/ |
|
Documentation and history describing how to use GIT and what happens when various common commands are used. Both porcelain and plumbing commands are considered. |
| HTTPS://GIT.BI6.US/TQT/ |
|
Documentation regarding the Quiet Type conventions and a parser to convert Quiet Type text files into a document tree which can be used by other tools. |
Cloning Public Repositories
To clone a public repository hosted here, simply use the git clone command with the repository's HTTPS URL.
For example, the command for cloning the TEST repository is:
$ git clone https://GIT.BI6.US/TEST/
By convention, this web site capitalizes domain names. The authority (domain name) of URLs listed here may be lower cased, but case is significant in the path section of the URL.
Submitting Changes to Public Repositories
Public repositories are read-only. There is no way to push a change to a repository hosted through the public interface. Consequently, the public interface does not support submitting a merge request.
You can, however, email a patch to the repository's maintainer. This acts as both a push and a pull request.
Suppose you wanted to change something in the repo at https://GIT.BI6.US/TEST/. To check out the repo, make a change, commit the change and then produce a patch, you would do something like this:
-
Check out the repo and note the current commit id:
The
clonecommand shouldn't be foreign to frequent git users. But we use therev-parsecommand to note the most recent commit id on the main branch.git clone https://GIT.BI6.US/TEST/ cd TEST git rev-parse HEAD
-
Make a change of some sort.
In the real world you would make a real change. But as an example, we're just going to create a new file with the current date in it.
date >> datefile.txt
-
Commit the change.
git add datefile.txt git commit -m "add date file"
-
Create the patch.
This works only if you've made a single local commit. The
git logcommand will show you a list of commits. Verify that there's only one new commit and then run theformat-patchcommand:git log git format-patch HEAD~1
If you've made multiple commits, it's okay. We just have to change the number after the
HEAD. If you've made 2 commits, you would use this command:git format-patch HEAD~2
If you made 3 commits, use this command:
git format-patch HEAD~3
The
format-patchcommand will create one patch file for each commit. Each execution of theformat-patchcommand will produce a new.patchfile with a name derived from a serial number and a portion of the commit message. For example, the first commit operation in the previous step would produce a patch file named0001-add-date-file.patch. -
(optional) Email the maintainer a patch
Each project has it's own maintainer, but if you can't find it or you get no response, email OhMeadhbh+git@gmail.com.
Document Metadata
| Author | Meadhbh Hamrick |
| Created | 2025-09-17T11:00:00-0700 |
| Revision | v1 |
| Canonical | HTTPS://GIT.BI6.US/ |