Git development
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@suse.cz>
To: Sitaram Chamarty <sitaramc@gmail.com>
Cc: Intland Software <marketing@intland.com>, git@vger.kernel.org
Subject: Re: [ANNOUNCE] codeBeamer MR - Easy ACL for Git
Date: Fri, 20 Nov 2009 08:47:02 +0100	[thread overview]
Message-ID: <20091120074702.GW12890@machine.or.cz> (raw)
In-Reply-To: <2e24e5b90911192056t706071ble163a53741017ef@mail.gmail.com>

  Hi!

On Fri, Nov 20, 2009 at 10:26:32AM +0530, Sitaram Chamarty wrote:
> On Thu, Nov 19, 2009 at 7:20 PM, Intland Software <marketing@intland.com> wrote:
> > * MR against Gitolite
> > Pretty much the same applies here as well.
> 
> Conceptually, gitolite can do the roles stuff you mentioned,
> if I understood it correctly.  Of course, gitolite's access
> config is in plain text.
> 
> The web-based control, issue tracking, etc., are all on a
> different plane from what gitosis/gitolite aim to be.  So
> much so that I might even disagree with Pasky on the need to
> mention these two products in your website.

I brought Gitosis/Gitolite up because I got the impression that MR was
marketed primarily as a Git ACL tool, the other things being sort of
mirror; maybe my impession was wrong, but I still think the comparison
in ACL capabilities is useful.

> You should stick to gitorious, github, and -- here's a new
> one for you -- indefero.

Hmm, I didn't even know about this one, thanks for the pointer. Looks
like this suddenly is a very popular area. High competition is good!

(BTW, if you don't care about wikis and issue tracking, but you do care
about simplicity and light-weightness, you should best stick to Girocco!
;-)

-- 
				Petr "Pasky" Baudis
A lot of people have my books on their bookshelves.
That's the problem, they need to read them. -- Don Knuth

  reply	other threads:[~2009-11-20  7:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-18  8:33 [ANNOUNCE] codeBeamer MR - Easy ACL for Git Intland Software
2009-11-18 12:09 ` Petr Baudis
2009-11-18 13:19   ` Intland Software
2009-11-19  6:06     ` david
2009-11-19 10:06       ` Intland Software
2009-11-19 10:43         ` Jakub Narebski
2009-11-19 12:15           ` Aron Gombas
2009-11-19 11:39     ` Rakotomandimby Mihamina
2009-11-19 13:50   ` Intland Software
2009-11-19 14:01     ` Thomas Rast
     [not found]       ` <4B05588B.5080501@intland.com>
2009-11-19 15:22         ` Intland Software
2009-11-20  4:56     ` Sitaram Chamarty
2009-11-20  7:47       ` Petr Baudis [this message]
2009-11-20  8:24         ` Intland Software
2009-11-21 13:12         ` Sitaram Chamarty
2009-11-23  9:34           ` Intland Software
2009-11-23 16:28             ` 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=20091120074702.GW12890@machine.or.cz \
    --to=pasky@suse.cz \
    --cc=git@vger.kernel.org \
    --cc=marketing@intland.com \
    --cc=sitaramc@gmail.com \
    /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