git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pete/Piet Delaney <pete@bluelane.com>
To: Git Mailing List <git@vger.kernel.org>,
	piet.delaney@gmail.piet.net,
	Piet Delaney <piet.delaney@gmail.com>
Subject: Re: Object Permissions - trying git-init --shared=group parameters
Date: Thu, 21 Feb 2008 14:06:39 -0800	[thread overview]
Message-ID: <47BDF5EF.9030707@bluelane.com> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Junio C Hamano wrote:
| Pete/Piet Delaney <pete@bluelane.com> writes:
|
|> I've been trying to us the git repo in a
|> centralize pull, push model where the
|> developers pull the repo, checkout a
|> branch, commit and then push back to the
|> common repo.
|>
|> Problem is that the objects get set with
|> the ownership of the user (at least when
|> pulling with this format:
|>
|> ~    git clone git:/home/git/blux
|>
|> Amy suggestions on how to do this?
|
| "man git-config" and look for core.sharedrepository, perhaps?

That's kinda what I'm trying. I did a git-init --shared=group
and found that it set:


	[core]
~        	repositoryformatversion = 0
~        	filemode = true
~        	bare = false
~        	logallrefupdates = true
~        	sharedrepository = 1

	[receive]
~        	denyNonFastforwards = true

So I looked int the meaning of these config prams and
thought I tried adding:

	sharedrepository = 1

	denyNonFastforwards = true

to the bare repo on the git server. I'm not sure if
existing repo that have been cloned will have to be
updated, hopefully not.

- -piet

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHvfXuJICwm/rv3hoRAl+PAJ9M/dRAuWRjs8gUvq1w3JqeH8/tNgCdFbto
iaqrDyOefH4zTEK8Zzximu4=
=xJM3
-----END PGP SIGNATURE-----

             reply	other threads:[~2008-02-21 22:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-21 22:06 Pete/Piet Delaney [this message]
2008-02-21 22:16 ` Object Permissions - trying git-init --shared=group parameters Junio C Hamano

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=47BDF5EF.9030707@bluelane.com \
    --to=pete@bluelane.com \
    --cc=git@vger.kernel.org \
    --cc=piet.delaney@gmail.com \
    --cc=piet.delaney@gmail.piet.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 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).