commit 66beee3c6fcf0a9a98bdf2efc4bcc7bcc9ac6572 (patch)
parent b9ebbed Use literal instead of listing for tree output
tree 625f7bc6ab03a5a24e3bb26466460a32702076d9
author Alyssa Ross <hi@alyssa.is> 2020-05-22 03:55:26 +0000
committer Alyssa Ross <hi@alyssa.is> 2020-05-22 03:55:26 +0000
HTTPS Creative Commons link
---
developer-manual.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/developer-manual.adoc b/developer-manual.adoc
index 63995fe..a538437 100644
--- a/developer-manual.adoc
+++ b/developer-manual.adoc
@@ -247,7 +247,7 @@ Copyright 2020 Alyssa Ross.
Permission is granted to copy, distribute and/or modify this document
under either the terms of the
-http://creativecommons.org/licenses/by-sa/4.0/[Creative Commons
+https://creativecommons.org/licenses/by-sa/4.0/[Creative Commons
Attribution-ShareAlike 4.0 International License], or the
https://www.gnu.org/licenses/fdl-1.3.html[GNU Free Documentation
License, Version 1.3] or any later version published by the Free
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