Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2025-07-31 02:29:32 -04:00
Code Issues Projects Releases Packages Wiki Activity
All Qubes OS Project documentation pages are stored as plain text files in this dedicated repository. By cloning and regularly pulling from this repo, users can maintain their own up-to-date offline copy of all Qubes documentation rather than relying solely on the Web.
6452 commits 6 branches 2605 tags 115 MiB
Find a file
Nina Eleanor Alter fca16e7f7f
Update how-to-update.md 
Per https://github.com/QubesOS/qubes-issues/issues/#6871 added a blurb in the CLI section, to advise users that 1. The terminal in the update-vm will in fact open, and 2. Where the logs will be saved to. My notation on two may be incorrect, so pls check?
2021-09-07 12:28:29 -07:00
_dev Use HTTPS everywhere (mechanical edit using util from https-everywhere) 2020-12-19 19:57:07 +01:00
developer Update "version scheme" 2021-09-06 23:06:13 -07:00
external Fix capitalization; update terms (QubesOS/qubes-issues#6769) 2021-07-09 05:10:44 -07:00
introduction Add link to "bug priorities" section 2021-09-06 22:51:30 -07:00
project-security Standardize orthography 2021-08-07 05:24:55 -07:00
user Update how-to-update.md 2021-09-07 12:28:29 -07:00
.gitlab-ci.yml gitlab-ci: use local project reference 2020-11-27 03:55:05 +01:00
.travis.yml Update travis to bionic 2020-09-29 15:12:04 +02:00
CONTRIBUTING.md Reorganize doc guidelines into multiple pages; update style guide 2021-07-08 08:08:57 -07:00
doc.md Update layout 2021-06-22 04:27:32 -07:00
README.md Reorganize doc guidelines into multiple pages; update style guide 2021-07-08 08:08:57 -07:00

README.md

Qubes OS Documentation

Canonical URL: https://www.qubes-os.org/doc/

All Qubes OS Project documentation pages are stored as plain text files in this dedicated repository. By cloning and regularly pulling from this repo, users can maintain their own up-to-date offline copy of all Qubes documentation rather than relying solely on the Web.

To contribute, please see how to edit the documentation.