I can't speak for gitosis -- I thank my stars every day that
the gitosis author did not reply to my emails back then,
because otherwise there may not have been a gitolite.
But I will try and address a couple of points which strike
me as important, especially ones that affect gitolite also,
just for completeness.
Gitolite will do the same thing. This is an artifact of the
fact that neither of them is looking *inside* the key and
comparing with others, coupled with the fact that sshd does
a linear scan, and when it finds a match it goes with it.
I can tell you that in gitolite, I have no intention of
adding that check by comparing the contents of the keys.
However, gitolite does have "sshkeys-lint" which will catch
the problem and tell you that second key will be ignored by
Good. A server side repo has no business having a working
tree ;-)
Gitolite was modelled after gitosis, although it's hard to
imagine that now, seeing how far apart they are today.
Server side repos == bare repos. Bare repos == .git suffix
as a convention in git-land. This convention becomes
"standard" in gitolite.
"cloning code into the repo on the local machine" -- if I
What I found more problematic was it would silently ignore
typos such as "member" instead of "members".
Gitolite will show you lots of errors.
You can still push up a botched-config (syntactically
correct but you managed to lock yourself out by typoing your
own name!), but you don't have to throw in the towel --
there is "gl-dont-panic" (written 2 months after "towel
day", to my eternal regret ;-)
Sitaram
--
