>-----Original Message----- >From: Sitaram Chamarty [mailto:sitaramc@xxxxxxxxx] >Sent: Thursday, October 28, 2010 5:02 PM >To: Olsen, Alan R >Cc: Matthieu Moy; git@xxxxxxxxxxxxxxx >Subject: Re: Bugs in Gitosis >On Fri, Oct 29, 2010 at 3:52 AM, Olsen, Alan R <alan.r.olsen@xxxxxxxxx> wrote: >> Does gitolite play well with Gerrit? I note in the docs that it does not react well to files under its control being messed with. >For the real reason I added that into the docs, see >http://github.com/sitaramc/gitolite/commit/10289c6d6494e7aa4204dfe29afec7535c1aa1a2 >If <any other software> wants to add *other* files into repos that >gitolite does not need, that is perfectly fine. Gitolite does not >expect to be "sole control", but just "don't mess with my stuff and >we'll get along fine". >However, I wasn't aware that it is even *possible* to run gerrit and >gitolite together. Gerrit has its own customised ssh daemon, its own >customised "git", and so on. Gerrit runs its ssh daemon on another port. If you run them both as the same user, it works fine. >I also fail to understand why you need gitolite if you're using >gerrit. I believe gerrit can do all the access control that gitolite >can do. See http://github.com/sitaramc/gitolite/blob/pu/contrib/gerrit.mkd >for a comparision We use gitosis currently for back-end management. Gerrit does not add existing projects well. Pushing the kernel project into Gerrit causes one entry to approve per commit. That swamps the server. Gerrit does not have a way of handling rebases very well. (We have projects that have a regular consolidation on the end of the development trees.) There are also some people (me for example) who loath the Repo command and prefer to work using git. I am hoping we can migrate to Gitolite. I am going to set up a test server to see if I can identify problems. ÿô.nlj·Ÿ®‰†+%ŠË±é¥Šwÿº{.nlj· ŠßžØn‡r¡öë¨è&£ûz¹Þúzf£¢·hšˆ§~††Ûÿÿïÿ‘ê_èæ+v‰¨þ)ßø