Explain updateable and private-to-the-repo information

[git-wiki.git] / pep-git.txt

diff --git a/pep-git.txt b/pep-git.txt
index af8fc37292c30a62537df299c7cc746a9a5012a2..a721a8538d3b566251f267143dc392a786917cd1 100644 (file)
--- a/pep-git.txt
+++ b/pep-git.txt
@@ -347,8 +347,7 @@ For example::
     $ git fetch origin v1:v1 tag 2.1.7
 
 Git doesn't automatically pushes tags. That allows you to have private
-tags (lightweight tags are also private for a repo, they cannot be
-pushed). To push tags list them explicitly::
+tags. To push tags list them explicitly::
 
     $ git push origin tag 1.4.2
     $ git push origin v1 v2 tag 2.1.7
@@ -356,6 +355,19 @@ pushed). To push tags list them explicitly::
 Don't move tags with ``git tag -f`` or remove tags with ``git tag -d``
 after they have been published.
 
+Private information
+'''''''''''''''''''
+
+When cloning/fetching/pulling/pushing git copies only database objects
+(commits, trees, files and tags) and symbolic references (branches and
+lightweight tags). Everything else is private to the repository and
+never cloned, updated or pushed. It's your config, your hooks, your
+private exclude file.
+
+If you want to distribute hooks, copy them to the working tree, add,
+commit, push and instruct the team to update ind install the hook
+manually.
+
 
 Commit editing and caveats
 ==========================