From: Samuel Lucas Vaz de Mello <samuellucas@datacom.ind.br>
To: git@vger.kernel.org
Subject: Re: Git newbie question: permissions
Date: Thu, 09 Oct 2008 18:05:54 -0300 [thread overview]
Message-ID: <48EE7232.5080107@datacom.ind.br> (raw)
In-Reply-To: <1b5a37350810091320l72ae0a86m39db4258c9f4827e@mail.gmail.com>
Ed Schofield wrote:
> I don't think I specified "--shared=group" when initializing the
> repository. Afterwards I manually set all files to have 660
> permissions, dirs as 770, and set the group ownership to "webdev", but
> I probably made a mistake by not setting the setgid bit on
> directories. Now there are some objects directories with 755
> permissions and different group ownership (the default groups of the
> other users).
>
Hi Ed!
I'm also a newbie here and I have a very similar setup to yours.
The only difference is that my repository was created using
git-cvsimport and afterwards I used git-config to set
core.sharedrepository=1 and manually set up the permissions.
I also got objects created with the users' default group, but for now I
just changed the deafault group for those users until I find a better
solution.
Another issue with this setup: if I run git-gc in the shared repo, it
recreate the files in logs/refs/heads with 644 permissions, which
prevents users to push until I manually fix the permissions.
Someone else have faced these kind of problems?
Regards,
- Samuel
next prev parent reply other threads:[~2008-10-09 21:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 20:20 Git newbie question: permissions Ed Schofield
2008-10-09 21:05 ` Samuel Lucas Vaz de Mello [this message]
2008-10-09 21:29 ` Marc Weber
2008-10-09 21:41 ` Samuel Tardieu
2008-10-09 22:59 ` Ed Schofield
2008-10-10 14:44 ` Samuel Lucas Vaz de Mello
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=48EE7232.5080107@datacom.ind.br \
--to=samuellucas@datacom.ind.br \
--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).