distributed version control

[Shai Ayal]

On Jan 28, 2008 6:37 PM, Rafael Laboissiere <rafael at debian.org> wrote:
> * David Bateman <David.Bateman at motorola.com> [2008-01-28 16:22]:
>
> > Don't pull and clone make a copy of the repository? What about
> > committing back to the master repository over https? I really have no
> > idea of the capabilities of the versioning tools proposed, and as SVN
> > was off the cards I haven't entered into this discussion till now.
>
> Well, git and hg works around a different model than that of cvs and svn.
> There is no "master repository" and "committing to a master repository"
> makes little sense with these tools.  Under this paradigm, every developer
> will have a private repository and will be able to pull or clone from JWE's
> repository (you could call JWE's repo the "master repo" but, in principle,
> it will be one repository like the others, besides the fact that John will
> use it for making the releases).
>
> Git has a git-push command that allows using it in a cvs- or svn-like
> manner, but I think we would better asking JWE to pull the changes from our
> repositories instead of falling back to the old version-control paradigm.

How is the pull done? do we email it to jwe, or do we need a server
that jwe can connect to?

Shai
Shai