Re: What a modern collaboration toolkit looks like

[David Kastrup <dak@gnu.org>]

Richard Stallman <rms@gnu.org> writes:

>     "the current development version" is not a concept for git.  No
>     repository is special as far as git is concerned.  The "current
>     development version" is a social, not a technical concept.  For example,
>     the git maintainer was off-line unexpectedly for some months recently.
>     Somebody else took over seamlessly by collecting, arranging and
>     coordinating patches on the git list into _his_ repository.
>
> With CVS, people can get the current version of every program on
> savannah in a uniform way.  What you say seems to imply that that is
> not possible with git.  That seems like a big step backwards.

Huh?  Declare a repository as official, and people can sync to it and
"get the current version of every program on Savannah in a uniform way".
They can sync to any other repository (or pull changes on top of other
already pulled changes), too, without disturbing their setup.  But it is
not like they would magically get something they didn't ask for, or
would not always be able to tell what changes in addition to the
Savannah remote state they had applied in their own repository.

> Within a community of people that work together, it won't be a
> problem.  They will know to look THERE instead of HERE.  But users in
> general can't be expected to check for that sort of thing before they
> get the current development Emacs.

Huh?  I can get an rsync of Emacs CVS, check something into that copy
and publish it on a server.  Same thing.  A user can't usefully work
with two CVS repositories at once, sure, but the THERE/HERE confusion is
just the same.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum