Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2024-10-01 01:25:40 -04:00
Code Issues Packages Projects Releases 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.
5,180 Commits 6 Branches 2,523 Tags 86 MiB
Makefile 51.8%
Python 48.2%
d5470f5a81
Go to file
Andrew David Wong d5470f5a81
Merge branch 'qrexec-internals-further-work' of https://github.com/pierwill/qubes-doc into pierwill-qrexec-internals-further-work
2020-01-23 03:56:09 -06:00
_dev _dev: add explanation 2018-04-18 21:16:59 +02:00
developer Merge branch 'qrexec-internals-further-work' of https://github.com/pierwill/qubes-doc into pierwill-qrexec-internals-further-work 2020-01-23 03:56:09 -06:00
external make sure the hostname is set 2020-01-15 09:58:35 +01:00
introduction Add entry for Load Kernel Modules message 2020-01-04 21:54:14 +00:00
project-security Recommend using gpg2 with keyserver options instead of gpg 2019-10-23 01:05:50 -05:00
user Merge branch 'disp-vm-fix' of https://github.com/tetrahedras/qubes-doc into tetrahedras-disp-vm-fix 2020-01-23 03:52:57 -06:00
.travis.yml Update rvm to 2.5 in .travis.yml 2019-12-09 00:00:18 -06:00
CONTRIBUTING.md Fix link 2017-04-04 21:52:06 -07:00
doc.md Merge branch 'qrexec-internals-further-work' of https://github.com/pierwill/qubes-doc into pierwill-qrexec-internals-further-work 2020-01-23 03:56:09 -06:00
README.md Fix typo 2016-03-22 22:52:54 +00: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.

For more information about the documentation, including how to contribute, please see the Documentation Guidelines.