Re: Painless namespaces design

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



2011/6/15 Jiang Xin <worldhello.net@xxxxxxxxx>:
> 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.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]