From 8568ada6ddde91e4cd53ae2351385bca4d7d6531 Mon Sep 17 00:00:00 2001
From: Alan Pearce
Date: Fri, 3 Apr 2020 21:44:24 +0200
Subject: Use more common front matter markers

---
 content/post/git-cloning-similar-repositories.md | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

(limited to 'content/post/git-cloning-similar-repositories.md')

diff --git a/content/post/git-cloning-similar-repositories.md b/content/post/git-cloning-similar-repositories.md
index 96ea7b4..517ff4d 100644
--- a/content/post/git-cloning-similar-repositories.md
+++ b/content/post/git-cloning-similar-repositories.md
@@ -1,10 +1,10 @@
-+++
-Categories = ["Development"]
-Description = "Speed up cloning of similar git repositories"
-Tags = ["git"]
-title = "Cloning Similar Git Repositories"
-date = 2014-06-22T08:35:24Z
-+++
+---
+Categories: ["Development"]
+Description: "Speed up cloning of similar git repositories"
+Tags: ["git"]
+title: "Cloning Similar Git Repositories"
+date: 2014-06-22T08:35:24Z
+---
 With multiple similar git repositories, for example where a base repository contains a framework or base system installation and other repositories are created from that repository, it's possible to save some time when cloning down another repository by using the `reference` option to [git-clone][]:
 
 	git clone git@github.com/my/repo --reference another-repo
@@ -16,4 +16,4 @@ On a related note, I'm surprised that [GitHub][] doesn't allow for multiple rena
 
 [git-clone]:https://www.kernel.org/pub/software/scm/git/docs/git-clone.html
 [GitHub]:https://github.com
-[BitBucket]:https://bitbucket.org/
\ No newline at end of file
+[BitBucket]:https://bitbucket.org/
-- 
cgit 1.4.1