From: Shawn Pearce <spearce@spearce.org>
To: Jiang Xin <worldhello.net@gmail.com>
Cc: Jamey Sharp <jamey@minilop.net>,
Junio C Hamano <gitster@pobox.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Jeff King <peff@peff.net>, Jakub Narebski <jnareb@gmail.com>,
Bert Wesarg <bert.wesarg@googlemail.com>,
git@vger.kernel.org
Subject: Re: Painless namespaces design
Date: Wed, 15 Jun 2011 07:00:00 -0700 [thread overview]
Message-ID: <BANLkTiktjki43wCX5d2SV+tKjp_fqmGznw@mail.gmail.com> (raw)
In-Reply-To: <4DF894FD.9040808@gmail.com>
2011/6/15 Jiang Xin <worldhello.net@gmail.com>:
> I like the idea of new namespaces feature from Josh Triplett, Jamey Sharp and others.
> I think it is better to pass namespace through remote.remote-name.namespace variables,
> not through GIT_NAMESPACE environment.
...
> [remote "origin"]
> namespace = foo
> fetch = +refs/heads/*:refs/remotes/origin/*
> url = ssh://Host1/path/to/project.git
>
> When UserA runs `git fetch`, it's just like
>
> git fetch origin refs/namespaces/foo/refs/heads/*:refs/remotes/origin/*
This is less than ideal. Part of the rationale for the GIT_NAMESPACE
environment variable is to allow the server to restrict the namespace
and only show that specific slice of the repository's refs to the
client. It allows a server administrator to put several logical
repositories into a single repository, and have clients be oblivious
to this fact.
--
Shawn.
prev parent reply other threads:[~2011-06-15 14:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 23:04 [PATCHv8 0/4] Support ref namespaces Jamey Sharp
2011-06-07 23:04 ` [PATCHv8 1/4] Fix prefix handling in ref iteration functions Jamey Sharp
2011-06-08 0:17 ` Junio C Hamano
2011-06-08 1:40 ` Josh Triplett
2011-06-07 23:04 ` [PATCHv8 2/4] Add infrastructure for ref namespaces Jamey Sharp
2011-06-07 23:04 ` [PATCHv8 3/4] Support ref namespaces for remote repositories via upload-pack and receive-pack Jamey Sharp
2011-06-07 23:04 ` [PATCHv8 4/4] Add documentation for ref namespaces Jamey Sharp
2011-06-08 15:19 ` Marc Branchaud
2011-06-15 11:18 ` Painless namespaces design Jiang Xin
2011-06-15 14:00 ` 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=BANLkTiktjki43wCX5d2SV+tKjp_fqmGznw@mail.gmail.com \
--to=spearce@spearce.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=bert.wesarg@googlemail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jamey@minilop.net \
--cc=jnareb@gmail.com \
--cc=peff@peff.net \
--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).