From: Junio C Hamano <gitster@pobox.com>
To: pete@bluelane.com
Cc: Git Mailing List <git@vger.kernel.org>, piet.delaney@gmail.piet.net
Subject: Re: Object Permissions
Date: Thu, 21 Feb 2008 12:58:50 -0800 [thread overview]
Message-ID: <7vir0it4ad.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <47BDDF27.2030603@bluelane.com> (pete@bluelane.com's message of "Thu, 21 Feb 2008 12:29:27 -0800")
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?
prev parent reply other threads:[~2008-02-21 20:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 20:29 Object Permissions Pete/Piet Delaney
2008-02-21 20:58 ` Junio C Hamano [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=7vir0it4ad.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=pete@bluelane.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).