On Wed, May 26, 2010 at 15:13, Matthias Fechner <idefix@xxxxxxxxxxx> wrote: > I hope that is the correct list to ask some questions. > I understood that the idea behind git is completely different and I like the > idea behind git. > > But for the svn repository I want to convert I need some features and I'm > not sure how / if to implement them in git. > > Corrently the svn repo is divided into trunk branches and tags. > In each of this directory like trunk i have directories like hardware, > software, docu and more. > > 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. No. Git isn't centralized. Anyone can clone the repo and change anything the want. You implement control by setting a policy on what you merge back into your tree, which is considered canonical. There are several on-commit filtering programs available that can do that automatically based on paths within the repository. > 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? There are a lot of these scripts available in contrib and elsewhere. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html