From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jon Loeliger <jdl@jdl.com>
Cc: Shawn Pearce <spearce@spearce.org>,
Junio C Hamano <junkio@cox.net>,
git@vger.kernel.org
Subject: Re: Setting up Password protected repositories?
Date: Sun, 17 Sep 2006 12:43:47 -0400 [thread overview]
Message-ID: <20060917164347.GA21710@fieldses.org> (raw)
In-Reply-To: <E1GOzP9-0001Fn-G8@jdl.com>
On Sun, Sep 17, 2006 at 11:22:03AM -0500, Jon Loeliger wrote:
> So, like, the other day Shawn Pearce mumbled:
> > Access is controlled by standard UNIX user/group read/write access
> > and ACLs if your OS/filesystem support them. You can also control
> > pushing with an update hook.
>
> OK. I seem to recall a recipe down this line somwhere... Is there
> a current "Best Practices" write up somewhere with these details
> outlined in it?
There's a few sentences in Documentation/cvs-migration.txt, and a little
more in Documentation/howto/update-hook-example.txt
--b.
prev parent reply other threads:[~2006-09-17 16:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-17 0:52 Setting up Password protected repositories? Jon Loeliger
2006-09-17 1:24 ` Junio C Hamano
2006-09-17 2:07 ` Jon Loeliger
2006-09-17 2:18 ` Junio C Hamano
2006-09-17 2:20 ` Shawn Pearce
2006-09-17 16:22 ` Jon Loeliger
2006-09-17 16:43 ` J. Bruce Fields [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=20060917164347.GA21710@fieldses.org \
--to=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=jdl@jdl.com \
--cc=junkio@cox.net \
--cc=spearce@spearce.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).