summaryrefslogtreecommitdiff
path: root/doc/distributed_version_control.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2011-03-04 12:31:01 -0400
committerGravatar Joey Hess <joey@kitenet.net>2011-03-04 12:31:01 -0400
commit69c14d130bc7a754e3a4fa184ff317690ad48ca6 (patch)
treeb669edb6488ded07ab2d7e105a9f05c9d8453d53 /doc/distributed_version_control.mdwn
parentc5c7eaf00917d8654c82de5a4b17465b354f8fbf (diff)
update
Diffstat (limited to 'doc/distributed_version_control.mdwn')
-rw-r--r--doc/distributed_version_control.mdwn13
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/distributed_version_control.mdwn b/doc/distributed_version_control.mdwn
new file mode 100644
index 000000000..f9cdb7e99
--- /dev/null
+++ b/doc/distributed_version_control.mdwn
@@ -0,0 +1,13 @@
+In git, there can be multiple clones of a repository, each clone can
+be independently modified, and clones can push or pull changes to
+one-another to get back in sync.
+
+git-annex preserves that fundamental distributed nature of git, while
+dropping the requirement that, once in sync, each clone contains all the data
+that was committed to each other clone. Instead of storing the content
+of a file in the repository, git-annex stores a pointer to the content.
+
+Each git-annex repository is responsible for storing some of the content,
+and can copy it to or from other repositories. [[Location_tracking]]
+information is committed to git, to let repositories inform other
+repositories what file contents they have available.