On Thu, Oct 20, 2005 at 12:11:20PM +0200, Arnaud Charlet wrote: > > DanJ put up a wiki page on the OpenSSH configuration (which really could be > > found with 3 minutes of googling, which is shorter than writing a mail > > asking > > information about it [not speaking of you, gaby]). > > Well, with all your respect, you seem to be living in a different world than > mine.
In my world, I work with plenty of existing CVS repositories that take longer to access than svn+ssh-without-connection caching, and it took me about five minutes to look up how to use OpenSSH connection caching once I knew that it existed. I wouldn't be heartbroken to work with svn without it. > In your world, everyone has an up-to-date version of every tool, > and have e.g. the latest OpenSSH and subversion clients installed > on his machine. In mine, this is clearly far from being the case: > no svn installed, and a 3.x openssh. Also in my world, building these in $HOME does not take very much effort. Would you feel better about the transition if someone tested and wrote up instructions on how to do this on various platforms? It's really quite easy. It's not like you need the new SSH server, just the unprivileged client. > So my gut feeling is that this switch is too early and that based on the > feedback received so far, we should aim at: > > - getting more feedback from as much people as possible (and saying "reminder: > the switch will occur in a week" was relatively effective at that ;-) > - getting as much improvements in svn 1.4 as possible > - switch when 1.4.x is out and considered stable enough so that people > can use it heavily Others have already said this better, but we've been planning this switch - and asking repeatedly for feedback - for a very long time now. We chose not to say "it will happen in a week" until we felt that everything was ready and most people were agreed, instead of deliberately baiting the community to solicit feedback. I think that was a good choice; I'm sorry that people are crawling out from every which way now to object to the entire idea. I eagerly look forward to svn. For me, the biggest draw is that cvs update on branches takes a heinously long time and svn update on branches does not. -- Daniel Jacobowitz CodeSourcery, LLC
