Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2024-12-25 07:19:33 -05:00
Code Issues Packages Projects Releases Wiki Activity

Resolve open issues mentioned on Transifex

Browse Source
This commit is contained in:
Tobias Killer 2021-04-16 19:45:56 +02:00
parent 7060c4a6fa
commit 617330d026
No known key found for this signature in database
GPG Key ID: 2DA5EF6F6E40B328
3 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
developer/building/development-workflow.md
View File

@ -19,7 +19,7 @@ assumes you're using qubes-builder to build Qubes.
# Repositories and committing Code
Qubes is split into a bunch of git repos. This are all contained in the
Qubes is split into a bunch of git repos. These are all contained in the
`qubes-src` directory under qubes-builder. Subdirectories there are separate
components, stored in separate git repositories.
@ -153,7 +153,7 @@ RPMS will appear in qubes-src/linux-kernel/pkgs/fc20/x86\_64:
if all repository are tagged with signed tag.
2. `make show-vtags` - show version of each component (based on git tags) -
mostly useful just before building ISO. **Note:** this will not show version
for components containing changes since last version tag
for components containing changes since last version tag.
3. `make push` - push change from **all** repositories to git server. You must
set proper remotes (see above) for all repositories first.
4. `make prepare-merge` - fetch changes from remote repositories (can be

2
developer/general/gsod.md
View File

@ -94,7 +94,7 @@ Here are some successful projects which have been implemented in the past by Goo
**Project**: Consolidate troubleshooting guides
**Brief explanation**: Troubleshooting guides are scattered across many pages and sometimes incomplete, leading to repeatedly posting the same instruction over and over when helping users to diagnose problems.
This could be helped by writing consolidated guide with with a clear list of symptom-action layout.
This could be helped by writing a consolidated guide with a clear list of symptom-action layout.
**Expected results**:

2
user/common-tasks/backup-restore.md
View File

@ -114,7 +114,7 @@ This brings up the **Qubes Restore VMs** window.
4. If your backup is encrypted, you must check the **Encrypted backup** box.
If a passphrase was supplied during the creation of your backup (regardless of whether it is encrypted), then you must supply it here.
**Note:** The passphrase which was supplied when the backup was created was used for **both** encryption/decryption and integrity verification.
**Note:** The passphrase which was supplied when the backup was created is used for **both** encryption/decryption and integrity verification.
If the backup was not encrypted, the supplied passphrase is used only for integrity verification.
All backups made from a Qubes R4.0 system will be encrypted.