From: Sitaram Chamarty <sitaramc@gmail.com>
To: "Olsen, Alan R" <alan.r.olsen@intel.com>
Cc: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Bugs in Gitosis
Date: Fri, 29 Oct 2010 05:32:14 +0530 [thread overview]
Message-ID: <AANLkTik+CcuAtB=t5GgP9C-WrJRZt-LDNs3wUChhKTuz@mail.gmail.com> (raw)
In-Reply-To: <26E9B811E137AB4B95200FD4C950886BA9665E50@orsmsx507.amr.corp.intel.com>
On Fri, Oct 29, 2010 at 3:52 AM, Olsen, Alan R <alan.r.olsen@intel.com> 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.
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
regards
sitaram
next prev parent reply other threads:[~2010-10-29 0:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 20:58 Bugs in Gitosis Olsen, Alan R
2010-10-28 21:42 ` Matthieu Moy
2010-10-28 22:22 ` Olsen, Alan R
2010-10-29 0:02 ` Sitaram Chamarty [this message]
2010-11-01 17:23 ` Olsen, Alan R
2010-11-01 17:32 ` Shawn O. Pearce
2010-10-28 23:54 ` Sitaram Chamarty
[not found] <AANLkTinzLL-Sk1cMd_3WNogmgvr=x4gEh7LuS8guNYgB@mail.gmail.com>
2010-10-29 10:52 ` Sitaram Chamarty
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTik+CcuAtB=t5GgP9C-WrJRZt-LDNs3wUChhKTuz@mail.gmail.com' \
--to=sitaramc@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=alan.r.olsen@intel.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).