packaging
/
ostree
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: fix swapped link syntax 

A few links in the docs had the Markdown syntax swapped like:

(link title)[link url]

Just cleaned up those.  Verified via `mkdocs serve`

Closes: #297
Approved by: cgwalters
This commit is contained in:
Micah Abbott 2016-05-12 16:54:06 -04:00 committed by Colin Walters (automation)
parent 817060e772
commit d451b87fbe
3 changed files with 4 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/manual/atomic-upgrades.md
View File

@ -45,7 +45,7 @@ operate "live" on the currently booted filesystem. The way they could
work with OSTree is instead to take the list of installed packages in work with OSTree is instead to take the list of installed packages in
the currently booted tree, and compute a new filesystem from that. A the currently booted tree, and compute a new filesystem from that. A
later chapter describes in more details how this could work: later chapter describes in more details how this could work:
[adapting-existing.md](Adapting Existing Systems). [Adapting Existing Systems](adapting-existing.md).
For the purposes of this section, let's assume that we have a For the purposes of this section, let's assume that we have a
newly generated filesystem tree stored in the repo (which shares newly generated filesystem tree stored in the repo (which shares
@ -56,7 +56,7 @@ checking it back out of the repo into a deployment.
Given a commit to deploy, OSTree first allocates a directory for Given a commit to deploy, OSTree first allocates a directory for
it. This is of the form `/boot/loader/entries/ostree-$osname-$checksum.$serial.conf`. it. This is of the form `/boot/loader/entries/ostree-$osname-$checksum.$serial.conf`.
The `$serial` is normally 0, but if a The `$serial` is normally `0`, but if a
given commit is deployed more than once, it will be incremented. given commit is deployed more than once, it will be incremented.
This is supported because the previous deployment may have This is supported because the previous deployment may have
configuration in `/etc` that we do not want to use or overwrite. configuration in `/etc` that we do not want to use or overwrite.

3
docs/manual/formats.md
View File

@ -125,8 +125,7 @@ the client executes.
This "updates as code" model allows for multiple content generation This "updates as code" model allows for multiple content generation
strategies. The design of this was inspired by that of Chromium: strategies. The design of this was inspired by that of Chromium:
[http://dev.chromium.org/chromium-os/chromiumos-design-docs/filesystem-autoupdate](ChromiumOS [ChromiumOS Autoupdate](http://dev.chromium.org/chromium-os/chromiumos-design-docs/filesystem-autoupdate).
autoupdate).
### The delta superblock ### The delta superblock

2
docs/manual/repo.md
View File

@ -98,7 +98,7 @@ that.
A later addition to OSTree is the concept of a "summary" file, created A later addition to OSTree is the concept of a "summary" file, created
via the `ostree summary -u` command. This was introduced for a few via the `ostree summary -u` command. This was introduced for a few
reasons. A primary use case is to be a target a reasons. A primary use case is to be a target a
(Metalink)[https://en.wikipedia.org/wiki/Metalink], which requires a [Metalink](https://en.wikipedia.org/wiki/Metalink), which requires a
single file with a known checksum as a target. single file with a known checksum as a target.
The summary file primarily contains two mappings: The summary file primarily contains two mappings: