From 492967a426e232c80a91d6b8c25097677a698288 Mon Sep 17 00:00:00 2001
From: Robert Morrison <sherlock5512@gmail.com>
Date: Tue, 5 Jul 2022 01:38:53 +0100
Subject: [PATCH] Adding Packer as a submodule

As this configuration uses Packer to manage its plugins I have decided
to add packer as a submodule. Only Time will tell if this was a bad idea
or not.

If neccessary I can always have some kind of code in my init that checks
if packer is available and if not uses git to pull it initally before
handing that job to packer
---
 .gitmodules      | 3 +++
 pack/packer.nvim | 1 +
 2 files changed, 4 insertions(+)
 create mode 100644 .gitmodules
 create mode 160000 pack/packer.nvim

diff --git a/.gitmodules b/.gitmodules
new file mode 100644
index 0000000..a179a18
--- /dev/null
+++ b/.gitmodules
@@ -0,0 +1,3 @@
+[submodule "pack/packer.nvim"]
+	path = pack/packer.nvim
+	url = https://github.com/wbthomason/packer.nvim
diff --git a/pack/packer.nvim b/pack/packer.nvim
new file mode 160000
index 0000000..d268d2e
--- /dev/null
+++ b/pack/packer.nvim
@@ -0,0 +1 @@
+Subproject commit d268d2e083ca0abd95a57dfbcc5d5637a615e219