From: "Dirk Süsserott" <newsletter@dirk.my1.cc>
To: Jeff King <peff@peff.net>
Cc: "Dirk Süsserott" <newsletter@dirk.my1.cc>,
"Ka-rlis Repsons" <karlis.repsons@gmail.com>,
git@vger.kernel.org
Subject: Re: use git-daemon by git://IP/path?
Date: Fri, 12 Jun 2009 16:41:01 +0200 [thread overview]
Message-ID: <4A3268FD.7000004@dirk.my1.cc> (raw)
In-Reply-To: <20090612141602.GB14628@coredump.intra.peff.net>
Am 12.06.2009 16:16 schrieb Jeff King:
> On Fri, Jun 12, 2009 at 03:54:08PM +0200, Dirk Süsserott wrote:
>
>>> Also, in general, how can it be set up, that >1 people have a write
>>> access to the same repository? Only by using the same login?
>> Have a look at the "--shared" option of "git init". That's supposed to
>
> I have also had good experiences with POSIX ACLs for sharing
> repositories:
>
> setfacl -R -m d:u:$user:rwX -m u:$user:rwX /path/to/repo
>
> which gets rid of dealing with group management. Of course your
> filesystem has to support them. :)
That's the best way, of course. We use it at work to have 'release'
repositories where only a dedicated maintainer and his deputy can
push to. Our developers push to their 'public' repos and the maintainer
then pulls their changes and pushes them to 'release' -- just like Junio
does here :-)
Dirk
next prev parent reply other threads:[~2009-06-12 14:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 12:13 use git-daemon by git://IP/path? Kārlis Repsons
2009-06-12 13:54 ` Dirk Süsserott
2009-06-12 14:16 ` Jeff King
2009-06-12 14:41 ` Dirk Süsserott [this message]
2009-06-12 14:24 ` git shared repository & permission problems Kārlis Repsons
2009-06-12 15:48 ` use git-daemon by git://IP/path? Pau Garcia i Quiles
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=4A3268FD.7000004@dirk.my1.cc \
--to=newsletter@dirk.my1.cc \
--cc=git@vger.kernel.org \
--cc=karlis.repsons@gmail.com \
--cc=peff@peff.net \
/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.