Re: policy and mechanism for less-connected clients

From: Jakub Narebski <jnareb@gmail.com>
Date: Jun 25, 2008, 09:30 UTC
Message-ID: <m37icdkgkl.fsf@localhost.localdomain>
In-Reply-To: <10634.0258535512$1214372002@news.gmane.org>

"David Jeske" <jeske@willowmail.com> writes:

Show 18 quoted lines

> -- Theodore Tso wrote:
> > ???
> > > 
> > > (a) safely "share" every DAG, branch, and tag data in their
> > > repository to a well-connected server, into an established
> > > namespace, while only changing branches and tags in their
> > > namespace. This will allow all users to see the changes of other
> > > users, without needing direct access to their trees (which are
> > > inaccessible behind firewalls). [1]
> >
> > Right, so thats github and/or git.or.cz. Each user gets his/her own
> > repository, but thats a very minor change. Not a big deal.
> 
> ...most notably, all their DAGs in a single repository to save space
> is important. Thousands of copies of thousands of repositories adds
> up. Especially when most of the users who want to commit something
> probably commit <1-10k of unique stuff. Seems pretty easy to change
> though. git.or.cz and github will both be wanting this eventually.

repo.or.cz has support for forks, i.e. sharing object database (for old objects) via alternates, although it is not "common object database" (as in, for example, $GIT_DIR/objects symlinked to single common parent repository)

GitHub has also some support for "forks", but as it is closed source I don't think anybody knows how it is done.

-- 
Jakub Narebski
Poland
ShadeHawk on #git