I think both hosts would do a fine job, so no strong opinion as to
where the other end of the wire physically ends up.

Very important to me though is that we get a ViewCVS 0.9.3 interface on
par with what we have now. There are a number of different flavours of
SCM-web interfaces around, but I've not met one as nice and usable as our
ViewCVS yet. (mostly I quite like ours and find all others I've tried to
be no where close) I depend on it heavily for diffs and exploring the
source tree + code history.

(with the support of the server admin there is no reason we can't run
multiple SCM-web interfaces on the same repo if diff't folks have diff't
preferences as to a particular web interface)


I think it is a very good idea to keep the active web page and source
code repos in the same place.

How to best archive the "grass" 5 repo without losing the change history?
If SCM moves away from intevation.de, we must expect that one day they
will want to turn the historical CVS server off.


Hamish

_______________________________________________
grass-dev mailing list
[email protected]
http://grass.itc.it/mailman/listinfo/grass-dev

Reply via email to