# Windows permissions with repository on a network share

3 messages from 2011-05-17 to 2011-05-18. Participants: Jerome Lovy, Sitaram Chamarty.
Thread: https://gitlist.dev/t/27382

## Jerome Lovy, 2011-05-17 15:25

Subject: Windows permissions with repository on a network share
Message-ID: <iqu417$qnj$1@dough.gmane.org>
URL: https://gitlist.dev/e/iqu417%24qnj%241%40dough.gmane.org

```
Hello,

Did anyone experiment with Windows permissions for a Git repository 
located on a Windows network share?

Is it a sensible scheme in order to have a central repository with ACLs 
(notably some group can read/write, some other group can only read) 
without the need to set up a dedicated server (ala Gitolite) ?
(Assuming a Windows network share infrastructure is already in place...)

TIA
Jérôme

```

## Sitaram Chamarty, 2011-05-18 08:52

Subject: Re: Windows permissions with repository on a network share
Message-ID: <BANLkTikb4Q9ZmG-ToaV5LXLzfrcBu58PUw@mail.gmail.com>
URL: https://gitlist.dev/e/BANLkTikb4Q9ZmG-ToaV5LXLzfrcBu58PUw%40mail.gmail.com
In-Reply-To: <iqu417$qnj$1@dough.gmane.org>

```
On Tue, May 17, 2011 at 8:55 PM, Jerome Lovy
<t2a2e9z8ncbs9qg@brefemail.com> wrote:
> Hello,
>
> Did anyone experiment with Windows permissions for a Git repository located
> on a Windows network share?
>
> Is it a sensible scheme in order to have a central repository with ACLs
> (notably some group can read/write, some other group can only read) without
> the need to set up a dedicated server (ala Gitolite) ?
> (Assuming a Windows network share infrastructure is already in place...)

I don't know about Windows but any OS/file-system level ACL system
that has more granularity than the usual user/group/other, ought to
work fine.

The only thing gitolite can add is branch-level permissions, which it
doesn't sound like you need.

[Of course, I like to think that the config file in gitolite is a much
cleaner way of setting, reviewing, changing, and tracking changes of,
permissions, but I'm biased ;-)]

```

## Jerome Lovy, 2011-05-18 10:10

Subject: Re: Windows permissions with repository on a network share
Message-ID: <4DD39B1A.2030401@brefemail.com>
URL: https://gitlist.dev/e/4DD39B1A.2030401%40brefemail.com
In-Reply-To: <BANLkTikb4Q9ZmG-ToaV5LXLzfrcBu58PUw@mail.gmail.com>

```
Le 18/05/2011 10:52, Sitaram Chamarty a écrit :
> On Tue, May 17, 2011 at 8:55 PM, Jerome Lovy
> <t2a2e9z8ncbs9qg@brefemail.com>  wrote:
>> Hello,
>>
>> Did anyone experiment with Windows permissions for a Git repository located
>> on a Windows network share?
>>
>> Is it a sensible scheme in order to have a central repository with ACLs
>> (notably some group can read/write, some other group can only read) without
>> the need to set up a dedicated server (ala Gitolite) ?
>> (Assuming a Windows network share infrastructure is already in place...)
>
> I don't know about Windows but any OS/file-system level ACL system
> that has more granularity than the usual user/group/other, ought to
> work fine.
>
> The only thing gitolite can add is branch-level permissions, which it
> doesn't sound like you need.
>
> [Of course, I like to think that the config file in gitolite is a much
> cleaner way of setting, reviewing, changing, and tracking changes of,
> permissions, but I'm biased ;-)]

In this respect, Gitolite has a good point indeed with the auditing 
possibility, thanks to change tracking.

```