Hello, we have a use case with groups of repositories which share lots of objects, but which are logically independent. There is no strict hierarchy between the repositories, the development modl is arbitrary. The alternates mechanism for sharig objects between repositories won't work. The best idea I came up with so far to solve this was to keep everything in the same repository on the server. Then, to keep the logically independent repositories separate, directories are used below refs/heads and refs/tags. Receive-pack and upload-pack are modified to hide this directory structure from clients so that repositories will continue to look "normal" to users. For example, the following structure on the server: refs/heads/one/master refs/tags/one/tag1 refs/heads/two/master refs/heads/two/branch2 would appear as two independent repositories to different clients: refs/heads/master refs/tags/tag1 and: refs/heads/master refs/heads/branch2 The following three patches implement this. What do you guys think -- does the basic idea and implementation look sensible, or am I overlooking a way to solve this kind of problem with other means? Thanks! receive-pack: Two small code cleanups Different views on a repository Different views on a repository: HEAD mapping Documentation/git-receive-pack.txt | 9 ++++- Documentation/git-upload-pack.txt | 10 +++++- builtin-receive-pack.c | 32 ++++++++++++++--- refs.c | 65 ++++++++++++++++++++++++++++++++++-- refs.h | 4 ++ upload-pack.c | 20 ++++++++++- 6 files changed, 127 insertions(+), 13 deletions(-) -- 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