aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJoey Hess <joey@kitenet.net>2010-06-09 13:45:18 -0400
committerJoey Hess <joey@kitenet.net>2010-06-09 13:45:18 -0400
commitbd59179e090d8443f4fbaa0f4c0ac586fc8dbbb3 (patch)
tree8590a8917f80325bfb1fd335258625e4232c3976 /doc
parent0da7b1a9c33b3ff67fade15c395672f02bfe6a45 (diff)
downloadikiwiki-bd59179e090d8443f4fbaa0f4c0ac586fc8dbbb3.tar
ikiwiki-bd59179e090d8443f4fbaa0f4c0ac586fc8dbbb3.tar.gz
response
Diffstat (limited to 'doc')
-rw-r--r--doc/setup/byhand/discussion.mdwn6
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/setup/byhand/discussion.mdwn b/doc/setup/byhand/discussion.mdwn
index 97ae40438..941976789 100644
--- a/doc/setup/byhand/discussion.mdwn
+++ b/doc/setup/byhand/discussion.mdwn
@@ -1 +1,7 @@
What directory is the 'working copy'? There can be two interpretations: the current dir and the .git dir.
+
+> It is fairly common terminology amoung all version control systems to use
+> "working copy" to refer to a checkout from version control, including
+> copies of all the versioned files, and whatever VCS-specific cruft that
+> entails. So, a working copy is everything you get when you `git clone`
+> a repository. --[[Joey]]