deac/gitolite
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

faq/tips: added "common errors..." section with 2 examples

Browse source
This commit is contained in:
Sitaram Chamarty 2009-09-11 23:03:41 +05:30
parent 694050d6c4
commit d9d432a483
1 changed files with 16 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
doc/3-faq-tips-etc.mkd
View file

@ -2,7 +2,8 @@
In this document: In this document:
* errors, warnings, notes... * common errors and mistakes
* other errors, warnings, notes...
* differences from gitosis * differences from gitosis
* error checking the config file * error checking the config file
* one user, many keys * one user, many keys
@ -10,7 +11,20 @@ In this document:
* cool ideas I want feedback on * cool ideas I want feedback on
* developer specific branches * 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. * 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 So at least one of your clients needs to have a recent git. Once at least