summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--doc/index.mdwn13
-rw-r--r--doc/summary.mdwn12
2 files changed, 13 insertions, 12 deletions
diff --git a/doc/index.mdwn b/doc/index.mdwn
index 0838505e8..47682349f 100644
--- a/doc/index.mdwn
+++ b/doc/index.mdwn
@@ -1,15 +1,4 @@
-git-annex allows managing files with git, without checking the file
-contents into git. While that may seem paradoxical, it is useful when
-dealing with files larger than git can currently easily handle, whether due
-to limitations in memory, checksumming time, or disk space.
-
-Even without file content tracking, being able to manage files with git,
-move files around and delete files with versioned directory trees, and use
-branches and distributed clones, are all very handy reasons to use git. And
-annexed files can co-exist in the same git repository with regularly
-versioned files, which is convenient for maintaining documents, Makefiles,
-etc that are associated with annexed files but that benefit from full
-revision control.
+[[!inline raw=yes pages="summary"]]
To get a feel for it, see the [[walkthrough]].
diff --git a/doc/summary.mdwn b/doc/summary.mdwn
new file mode 100644
index 000000000..458eaab56
--- /dev/null
+++ b/doc/summary.mdwn
@@ -0,0 +1,12 @@
+git-annex allows managing files with git, without checking the file
+contents into git. While that may seem paradoxical, it is useful when
+dealing with files larger than git can currently easily handle, whether due
+to limitations in memory, checksumming time, or disk space.
+
+Even without file content tracking, being able to manage files with git,
+move files around and delete files with versioned directory trees, and use
+branches and distributed clones, are all very handy reasons to use git. And
+annexed files can co-exist in the same git repository with regularly
+versioned files, which is convenient for maintaining documents, Makefiles,
+etc that are associated with annexed files but that benefit from full
+revision control.