On Wed, Jun 06, 2001 at 10:29 +0200, Michal Svec wrote: > > How far is the IPv6 support in cvs? This falls into the same category discussed in length (and heat) lately: Should CVS care? Nope. Not a second. It's the admin's job to plug the tools together which best fit a certain environment. And there's no reason for bloat (read: unrelated code) in a program already so big in functionality and size. Resources are better spent when focused to control versioning. :) As long as your $CVS_RSH command supports whatever topology or features you demand when talking over some net (strictly speaking: between a client and a server with *anything* in between, not necessarily a network) you're free to do whatever you want to. CVS isn't even remotely involved. The client simply forks off a "$CVS_RSH [-l $USER] $HOST cvs server" command while the server side ("cvs server") just reads from stdin and talks to stdout. That should be simple and most of all portable. Yet flexible (you can use IPv6 today without updating any part of CVS). Just as much as there's no need to implement any security features in CVS (and to fail in doing it right for the first ten or twenty tries) there's no need for networking code inside a VC system. But maybe it's just me thinking so ... virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" [EMAIL PROTECTED] -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs