git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Pearce <spearce@spearce.org>
To: Sverre Rabbelier <srabbelier@gmail.com>, weigelt@metux.de
Cc: git@vger.kernel.org
Subject: Re: limiting ref visibility to specific users
Date: Tue, 17 Aug 2010 09:55:26 -0700	[thread overview]
Message-ID: <AANLkTi=aSwu0JttExA8CN=2GhFYwt10+cCvUR77jibmj@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikbT+e+7+LxrP6TkuuQ=8rMxuTnvFcUbUFzaUgk@mail.gmail.com>

On Tue, Aug 17, 2010 at 8:48 AM, Sverre Rabbelier <srabbelier@gmail.com> wrote:
> On Tue, Aug 17, 2010 at 10:09, Enrico Weigelt <weigelt@metux.de> wrote:
>> I'd like to control which refs are visible to certain users
>> (when coming via ssh). Is there already some generic way to
>> do that (eg. passing some filter rule by a calling wrapper ?)
>
> Shawn, weren't you looking into something similar for Gerrit? Although
> I think what you were investigating would allow the user to get the
> rest of the refs somehow?

Yup.  We implemented this in JGit by allowing the application to
provide an implementation of a RefFilter interface, only the refs that
the filter approves are shown to the remote client.  During
receive-pack (server side of push) the RefFilter also is used to
restrict what objects the client may mention as a delta base, or as an
object in the graph (e.g. commit parent, commit root tree, or tree
entry member).

There is no equivalent in C Git.  You have to use either Gerrit Code
Review, or build your own server on top of JGit to take advantage of
that feature.

-- 
Shawn.

      reply	other threads:[~2010-08-17 16:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-17 15:09 limiting ref visibility to specific users Enrico Weigelt
2010-08-17 15:48 ` Sverre Rabbelier
2010-08-17 16:55   ` Shawn Pearce [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='AANLkTi=aSwu0JttExA8CN=2GhFYwt10+cCvUR77jibmj@mail.gmail.com' \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=srabbelier@gmail.com \
    --cc=weigelt@metux.de \
    /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).