From: Greg Troxel <gdt@ir.bbn.com>
To: Robert Buck <buck.robert.j@gmail.com>
Cc: "git\@vger.kernel.org List" <git@vger.kernel.org>
Subject: Re: [remote rejected] master -> master (n/a (unpacker error))
Date: Thu, 13 May 2010 08:05:00 -0400 [thread overview]
Message-ID: <rmiy6fo3t3n.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: <AANLkTilz_gbHl_RLyOuvEIdjPoUDIfZTUCpnswdHTiej@mail.gmail.com> (Robert Buck's message of "Thu, 13 May 2010 05:30:43 -0400")
[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]
Robert Buck <buck.robert.j@gmail.com> writes:
> Yes, the repository is shared by several people, and in geographically
> different locations, ssh-ing to the same host, under different groups.
> So your recommendation would be to use --shared. But this won't work
> so well out in the wild will it? Meaning, what if people's accounts
> are NOT under the same group that is?
Git simply rides on filesystem permissions. So you choose a group to
control access to the repository, chgrp -R the repo to that group, and
config shared=0660. Then you put people in the group to give them
access; it doesn't have to be their primary gid. I don't follow your
objection; you seem to want to use groups to control access yet not set
up a group for the repo.
On some systems (e.g. BSD), directories automatically inherit the parent
dir's group. On others, you need setgid bit. I have the impression
that git will deal with this all correctly if you simply have
"sharedrepository = 0660" under [core] in config; I would expect it to
chgrp new files/dirs as needed to match the repo dir's group.
I don't see how chroot would change the issues above.
[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]
next prev parent reply other threads:[~2010-05-13 12:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 19:45 [remote rejected] master -> master (n/a (unpacker error)) Robert Buck
2010-05-13 0:06 ` Chris Packham
2010-05-13 0:52 ` Jonathan Nieder
2010-05-13 9:30 ` Robert Buck
2010-05-13 12:05 ` Greg Troxel [this message]
2010-05-13 13:22 ` Andreas Schwab
2010-05-13 13:56 ` Jonathan Nieder
2015-11-27 21:37 ` DavidLeeCrites
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=rmiy6fo3t3n.fsf@fnord.ir.bbn.com \
--to=gdt@ir.bbn.com \
--cc=buck.robert.j@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).