* Windows permissions with repository on a network share @ 2011-05-17 15:25 Jerome Lovy 2011-05-18 8:52 ` Sitaram Chamarty 0 siblings, 1 reply; 3+ messages in thread From: Jerome Lovy @ 2011-05-17 15:25 UTC (permalink / raw) To: git 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 ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Windows permissions with repository on a network share 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 0 siblings, 1 reply; 3+ messages in thread From: Sitaram Chamarty @ 2011-05-18 8:52 UTC (permalink / raw) To: Jerome Lovy; +Cc: git 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 ;-)] ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Windows permissions with repository on a network share 2011-05-18 8:52 ` Sitaram Chamarty @ 2011-05-18 10:10 ` Jerome Lovy 0 siblings, 0 replies; 3+ messages in thread From: Jerome Lovy @ 2011-05-18 10:10 UTC (permalink / raw) To: Sitaram Chamarty; +Cc: git 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. ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-05-18 10:12 UTC | newest] Thread overview: 3+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 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 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).