git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 20:35:45 +0800	[thread overview]
Message-ID: <856bfe0e0812170435t32fce496q41f825c01ee7045c@mail.gmail.com> (raw)
In-Reply-To: <bd6139dc0812170353y5d78f03ao1c0619c9bd68f309@mail.gmail.com>

Sverre,
Thank you for your information !
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 ?

I'll look at github and gitorious, are they free software ?

Thanks,
Emily


On Wed, Dec 17, 2008 at 7:53 PM, Sverre Rabbelier <srabbelier@gmail.com> wrote:
> On Wed, Dec 17, 2008 at 10:15, Emily Ren <lingyan.ren@gmail.com> wrote:
>> I want some group can pull these branches or tags from my repo, while
>> other's can't, Need I maintain two repositories ?
>
> I think gitosis should be able to do that? Otherwise you could look
> into hosting sites like github or gitorious, I think they have at
> least some form of access control, yes?
>
> --
> Cheers,
>
> Sverre Rabbelier
>

  reply	other threads:[~2008-12-17 12:44 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 [this message]
2008-12-17 12:47         ` Sverre Rabbelier
2008-12-17 13:37           ` Emily Ren
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=856bfe0e0812170435t32fce496q41f825c01ee7045c@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).