From d9d432a483ffc3c8e7228713bef7cc8de9c74829 Mon Sep 17 00:00:00 2001 From: Sitaram Chamarty Date: Fri, 11 Sep 2009 23:03:41 +0530 Subject: [PATCH] faq/tips: added "common errors..." section with 2 examples --- doc/3-faq-tips-etc.mkd | 18 ++++++++++++++++-- 1 file changed, 16 insertions(+), 2 deletions(-) diff --git a/doc/3-faq-tips-etc.mkd b/doc/3-faq-tips-etc.mkd index 4fc44b1..2f65fa2 100644 --- a/doc/3-faq-tips-etc.mkd +++ b/doc/3-faq-tips-etc.mkd @@ -2,7 +2,8 @@ In this document: - * errors, warnings, notes... + * common errors and mistakes + * other errors, warnings, notes... * differences from gitosis * error checking the config file * one user, many keys @@ -10,7 +11,20 @@ In this document: * cool ideas I want feedback on * developer specific branches -### errors, warnings, notes... +### common errors and mistakes + + * forgetting to suffix `.git` to the end of the reponame in the `git clone`. + This suffix is *not* used in the gitolite config file for the sake of + clarity and cleaner syntax, but don't let that fool you. It's a + convention in the git world that **bare repos** end with `.git`. + + * adding `repositories/` at the start of the repo name in the `git clone`. + This error is typically made by the *admin* himself -- because he knows + what `$REPO_BASE` is set to and thinks he has to provide that prefix on + the client side also :-) In fact gitolite prepends `$REPO_BASE` when it + is required anyway, so you shouldn't do the same thing! + +### other errors, warnings, notes... * cloning an empty repo is only possible with clients greater than 1.6.2. So at least one of your clients needs to have a recent git. Once at least