git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nazri Ramliy <ayiehere@gmail.com>
To: Matthias Fechner <idefix@fechner.net>
Cc: git@vger.kernel.org
Subject: Re: Migrate from svn to git
Date: Thu, 27 May 2010 01:04:11 +0800	[thread overview]
Message-ID: <AANLkTilNlttIQxyhMJz8_wiOQX5OaL0UahsE54mv6rQ3@mail.gmail.com> (raw)
In-Reply-To: <4BFD3AAF.4080403@fechner.net>

On Wed, May 26, 2010 at 11:13 PM, Matthias Fechner <idefix@fechner.net> wrote:
> For each of this subdirectories I have usergroups defined which has no
> access, read access or rw access.
>
> If I understood the manual correctly I can stick on that structure and
> easily work here with the unix-permission to grant access to the folders?
> I think I have to test then acl with freebsd to have more then one group for
> each directory.

Dealing with acl sounds like a lot of work and complications to me.
Have a look at gitolite. It is covered quite nice in the progit book [1]

> The second question is, I someone commits some files with svn an email is
> sent to a svn-commit mailinglist so changes can easily be discussed.
> The current mail is sent in html format with a colored diff, so it is easier
> to read.
>
> Is something similar possible with git or do you suggest a complete
> approach?

For this you might want to look at Gerrit [2]. It's a web-based code
review. Although it is not email based (AFAIK).

nazri.


[1] http://progit.org/book/ch4-8.html
[2] http://code.google.com/p/gerrit/

  parent reply	other threads:[~2010-05-26 17:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-26 15:13 Migrate from svn to git Matthias Fechner
2010-05-26 16:23 ` Ævar Arnfjörð Bjarmason
2010-05-27  6:22   ` Matthias Fechner
2010-05-26 16:26 ` hasen j
2010-05-26 17:04 ` Nazri Ramliy [this message]
2010-05-27  6:19   ` Matthias Fechner
2010-05-31 12:01 ` Michael Witten
2010-06-01  6:51   ` Matthias Fechner
2010-06-01 14:23     ` Michael Witten

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=AANLkTilNlttIQxyhMJz8_wiOQX5OaL0UahsE54mv6rQ3@mail.gmail.com \
    --to=ayiehere@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=idefix@fechner.net \
    /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).