commit b9ebbeda71e94d6085906aa4c379989962d2933d (patch)
parent 20a65f5 Mention spectrum-vm in crosvm documentation
tree 525957f8701686d1e07189feba55943deb7dd487
author Alyssa Ross <hi@alyssa.is> 2020-05-11 19:27:40 +0000
committer Alyssa Ross <hi@alyssa.is> 2020-05-11 19:27:40 +0000
Use literal instead of listing for tree output
This feels more appropriate since tree output isn't really a source
code listing.
Thanks-to: Jonas Höglund <firefly@firefly.nu>
---
developer-manual.adoc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/developer-manual.adoc b/developer-manual.adoc
index f96202e..63995fe 100644
--- a/developer-manual.adoc
+++ b/developer-manual.adoc
@@ -121,7 +121,7 @@ components.
So, you should check out the https://spectrum-os.org/git/crosvm[crosvm
repository] into a hierarchy that looks something like this:
-----
+....
chromiumos/
├── aosp/
│ └── external/
@@ -130,7 +130,7 @@ chromiumos/
│ └── crosvm/ (git clone https://spectrum-os.org/git/crosvm)
└── third_party/
└── adhd/ (git clone https://chromium.googlesource.com/chromiumos/third_party/adhd)
-----
+....
The exact other components required by crosvm depend on what build
options you're using and will also likely change over time. So the
glossary
--------
Commit objects reference one tree, and zero or more parents.
Single parent commits can typically generate a patch in
unified diff format via `git format-patch'.
Multiple parents means the commit is a merge.
Root commits have no ancestor. Note that it is
possible to have multiple root commits when merging independent histories.
Every commit references one top-level tree object.
git clone https://inbox.spectrum-os.org/doc