From: Jerome Lovy <t2a2e9z8ncbs9qg@brefemail.com>
To: git@vger.kernel.org
Subject: Windows permissions with repository on a network share
Date: Tue, 17 May 2011 17:25:28 +0200 [thread overview]
Message-ID: <iqu417$qnj$1@dough.gmane.org> (raw)
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
next reply other threads:[~2011-05-17 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 15:25 Jerome Lovy [this message]
2011-05-18 8:52 ` Windows permissions with repository on a network share Sitaram Chamarty
2011-05-18 10:10 ` Jerome Lovy
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='iqu417$qnj$1@dough.gmane.org' \
--to=t2a2e9z8ncbs9qg@brefemail.com \
--cc=git@vger.kernel.org \
/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 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).