From: Sitaram Chamarty <sitaramc@gmail.com>
To: Jiang Xin <worldhello.net@gmail.com>
Cc: Git List <git@vger.kernel.org>,
Josh Triplett <josh@joshtriplett.org>,
Jamey Sharp <jamey@minilop.net>
Subject: Re: Access different NAMESPACE of remote repo from client side
Date: Sat, 16 Nov 2013 14:43:30 +0530 [thread overview]
Message-ID: <5287373A.8030604@gmail.com> (raw)
In-Reply-To: <CANYiYbHzHEFLshU8r-m=0CUo7JTu-iyv1W4N291hX8+r1BYY-w@mail.gmail.com>
On 11/16/2013 01:30 PM, Jiang Xin wrote:
> 2013/11/15 Sitaram Chamarty <sitaramc@gmail.com>:
>> On 11/15/2013 07:55 PM, Sitaram Chamarty wrote:
[snip]
>> I should add that the Gitolite model is: the user doesn't need to know
>> about namespaces, because namespaces are just things that the server
>> admin is setting up for his own reasons...
>>
>
> I want to say something that git-namespace is sometimes significant
> for normal user not only for admin.
Sure. I only meant in the model that I wrote that branch for.
But consider a slight change of syntax:
repo dev/CREATOR/..*
C = @team
RW+ = CREATOR
R = @all
option namespace.pattern-1 = dev/%/%/NS/* is @1/@3 in @2
Let's say linux and git are parent repos already created (maybe earlier
in the conf).
This conf will let you use URLs like
dev/u1/git/NS/bar (becomes namespace u1/bar in git)
dev/u2/git/NS/baz (becomes namespace u2/baz in git)
Yeah it looks like a kludge, but all I wanted to do was to show you that
it's not entirely true to say the client cannot control the namespace!
prev parent reply other threads:[~2013-11-16 9:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 8:19 Access different NAMESPACE of remote repo from client side Jiang Xin
2013-11-15 9:49 ` [PATCH] shell: allow git command with --namespace option Jiang Xin
2013-11-15 14:25 ` Access different NAMESPACE of remote repo from client side Sitaram Chamarty
2013-11-15 14:47 ` Sitaram Chamarty
2013-11-16 8:00 ` Jiang Xin
2013-11-16 9:13 ` Sitaram Chamarty [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=5287373A.8030604@gmail.com \
--to=sitaramc@gmail.com \
--cc=git@vger.kernel.org \
--cc=jamey@minilop.net \
--cc=josh@joshtriplett.org \
--cc=worldhello.net@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).