From: Michael J Gruber <git@drmicha.warpmail.net>
To: Andreas Gruenbacher <agruen@suse.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/3] Different views on a repository
Date: Thu, 25 Feb 2010 10:01:43 +0100 [thread overview]
Message-ID: <4B863C77.8040304@drmicha.warpmail.net> (raw)
In-Reply-To: <92fea2335b73265b04d64fcc217055e1170f5e16.1267029680.git.agruen@suse.de>
Andreas Gruenbacher venit, vidit, dixit 24.02.2010 16:57:
> Add --view options in upload-pack and receive-pack so that a repository
> on the server side can be made to look like several independent
> repositories on the client side.
>
> This is implemented by transforming ref names: for example, with
> --view=one/, refs/heads/one/master on the server will look like
> refs/heads/master to the client, refs/tags/one/v1 will look like
> refs/tags/v1, etc.
>
> This allows to transparently share repositories on the server which
> have a lot of objects in common without complicating things for the
> client, and without breaking garbage collection.
Just from this description, I can't see why the same can't be done with
appropriate refspecs. (A helper for doing that would be more welcome, of
course.)
Maybe a few tests and documentation (i.e. examples, not just the option
description) would clear this up?
Michael
next prev parent reply other threads:[~2010-02-25 9:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 16:41 [RFC][PATCH 0/3] Different views on a repository Andreas Gruenbacher
2010-02-24 15:33 ` [PATCH 1/3] receive-pack: Two small code cleanups Andreas Gruenbacher
2010-02-24 15:57 ` [PATCH 2/3] Different views on a repository Andreas Gruenbacher
2010-02-24 16:14 ` [PATCH 3/3] Different views on a repository: HEAD mapping Andreas Gruenbacher
2010-02-24 17:42 ` [PATCH 2/3] Different views on a repository Shawn O. Pearce
2010-02-25 9:01 ` Michael J Gruber [this message]
2010-02-25 9:25 ` Andreas Gruenbacher
2010-02-25 12:30 ` Michael J Gruber
2010-02-25 14:35 ` Andreas Gruenbacher
2010-02-25 17:28 ` Junio C Hamano
2010-02-26 0:45 ` Andreas Gruenbacher
2010-02-26 21:35 ` Andreas Gruenbacher
2010-02-24 17:29 ` [PATCH 1/3] receive-pack: Two small code cleanups Shawn O. Pearce
2010-02-25 20:13 ` [RFC][PATCH 0/3] Different views on a repository James Pickens
2010-02-26 4:30 ` Adam Brewster
[not found] ` <c376da901002252012s507a6921q922e606bdce4b4fa@mail.gmail.com>
2010-02-26 12:01 ` Andreas Gruenbacher
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=4B863C77.8040304@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=agruen@suse.de \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.