git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Windows permissions with repository on a network share

From
Sitaram Chamarty <sitaramc@gmail.com>
Date
May 18, 2011, 08:52 UTC
Message-ID
<BANLkTikb4Q9ZmG-ToaV5LXLzfrcBu58PUw@mail.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:

Show 9 quoted lines
> 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 ;-)]

Previous: Jerome LovyNext: Jerome Lovy
Message 2 of 3 in “Windows permissions with repository on a network share”
  1. Jerome LovyMay 17, 2011
  2. Sitaram ChamartyMay 18, 2011
  3. Jerome LovyMay 18, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.