From: "Emily Ren" <lingyan.ren@gmail.com>
To: "Sverre Rabbelier" <srabbelier@gmail.com>
Cc: "Git Mailinglist" <git@vger.kernel.org>
Subject: Re: Can I forbid somebody to pull some branch or tag from my repo with git protocol?
Date: Wed, 17 Dec 2008 21:37:36 +0800 [thread overview]
Message-ID: <856bfe0e0812170537n78abbd57pfe33b3829941ebb9@mail.gmail.com> (raw)
In-Reply-To: <bd6139dc0812170447h7546cbf0v3151166668ad1248@mail.gmail.com>
Sverre, Johannes,
Thank you very much for sharing your good idea ! Yes, maintaining two
separate rep maybe best.
Johannes,
Does your second suggestion mean that I need to write a script and use
git hook to enable it ?
Thanks,
Emily
On Wed, Dec 17, 2008 at 8:47 PM, Sverre Rabbelier <srabbelier@gmail.com> wrote:
> [It is common not to top-post on this list :)]
>
> On Wed, Dec 17, 2008 at 13:35, Emily Ren <lingyan.ren@gmail.com> wrote:
>> As far as I know, gitosis can control someone readonly/writable to
>> some repo, it has no access control on branch/tag level. Am I right ?
>
> Ah, sorry, I meant to control access to different repo's for different groups.
>
>> I'll look at github and gitorious, are they free software ?
>
> IIRC gitorious is open source, but I just checked and I don't see any
> access control there; which leaves github, which is not free software
> I'm afraid.
>
> I think, as Johannes said, keeping two seperate repo's and using some
> form of access control on those would be best.
>
> --
> Cheers,
>
> Sverre Rabbelier
>
next prev parent reply other threads:[~2008-12-17 13:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-17 9:03 Can I forbid somebody to pull some branch or tag from my repo with git protocol? Emily Ren
2008-12-17 9:09 ` Junio C Hamano
2008-12-17 9:15 ` Emily Ren
2008-12-17 11:53 ` Sverre Rabbelier
2008-12-17 12:35 ` Emily Ren
2008-12-17 12:47 ` Sverre Rabbelier
2008-12-17 13:37 ` Emily Ren [this message]
2008-12-17 12:25 ` Johannes Schindelin
2008-12-17 19:36 ` Junio C Hamano
2008-12-17 12:12 ` Johannes Schindelin
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=856bfe0e0812170537n78abbd57pfe33b3829941ebb9@mail.gmail.com \
--to=lingyan.ren@gmail.com \
--cc=git@vger.kernel.org \
--cc=srabbelier@gmail.com \
/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).