|author||Austin Adams <email@example.com>||2017-03-09 23:38:53 -0500|
|committer||Austin Adams <firstname.lastname@example.org>||2017-03-09 23:38:53 -0500|
recent-commits-hugo: Fix typo
1 files changed, 2 insertions, 2 deletions
diff --git a/content/blog/including-recent-commits-hugo.md b/content/blog/including-recent-commits-hugo.md
index 1a46a32..a7ed1ab 100644
@@ -53,8 +53,8 @@ parents!
My first idea for traversal was brute force; that is, looking at every
dang commit in the repository and then sorting them by date. However,
-for gigantic repositories like the Linux kernel, this approach
-introduces searches much more of the commit graph than necessary.
+for gigantic repositories like the Linux kernel, this approach searches
+much more of the commit graph than necessary.
To inspect as little of the graph as possible while still finding recent
commits, I settled on a [breadth-first search] which stops after