From: Jerome Lovy <t2a2e9z8ncbs9qg@brefemail.com>
To: Sitaram Chamarty <sitaramc@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Windows permissions with repository on a network share
Date: Wed, 18 May 2011 12:10:34 +0200 [thread overview]
Message-ID: <4DD39B1A.2030401@brefemail.com> (raw)
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.
prev parent reply other threads:[~2011-05-18 10:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 15:25 Windows permissions with repository on a network share Jerome Lovy
2011-05-18 8:52 ` Sitaram Chamarty
2011-05-18 10:10 ` Jerome Lovy [this message]
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=4DD39B1A.2030401@brefemail.com \
--to=t2a2e9z8ncbs9qg@brefemail.com \
--cc=git@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.