aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDaniel J. H. <daniel+github@trvx.org>2013-04-19 04:40:55 +0300
committerDaniel J. H. <daniel+github@trvx.org>2013-04-19 04:40:55 +0300
commit60fd9b0303ef4af5538663bc1a502e23f3f472b8 (patch)
treec21024154a2cf413550d6e250dbd62e4d48bd7cb
parentf1d22a17286055f7ca32e885998f1814c2eed302 (diff)
downloadpelican-themes-60fd9b0303ef4af5538663bc1a502e23f3f472b8.tar.gz
Clone repository recursively, submodule'ed themes
Git submodules are great to keep track of themes without having to manage them all in one repository. But cloning the main repository only gets you empty folders for the submodules; an additional init is needed. It's easier and more convenient to just clone the main repository recursively, in order to pull in all themes.
-rw-r--r--README.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.rst b/README.rst
index 02bd5fc..f6118df 100644
--- a/README.rst
+++ b/README.rst
@@ -18,7 +18,7 @@ directory ``~/pelican-themes``, but yours could be different. Clone the
.. code-block:: sh
- git clone https://github.com/getpelican/pelican-themes ~/pelican-themes
+ git clone --recursive https://github.com/getpelican/pelican-themes ~/pelican-themes
Now you should have your ``pelican-themes`` repository stored at
``~/pelican-themes/``.