Re: [Jmol-developers] SVN access problem

2015-07-29 Thread Robert Hanson
I support this idea in principle; I just started using Git on another project (Jalview), and I certainly see the advantages. No system is immune to failure, but it is true that the local repository aspect of Git does mean there cannot be a catastrophic failure that impacts us for weeks the way we

Re: [Jmol-developers] SVN access problem

2015-07-28 Thread Andreas Prlic
I'd strongly support a move to github. It is so much better in so many ways... Andreas On Mon, Jul 27, 2015 at 12:41 PM, Herman Bergwerf hermanbergw...@gmail.com wrote: Perhaps time to move to GitHub? (not sure about the limitations) On Mon, Jul 27, 2015, 13:24 Nicolas Vervelle

Re: [Jmol-developers] SVN access problem

2015-07-27 Thread Michael Banck
On Mon, Jul 27, 2015 at 01:02:17PM +0200, Nicolas Vervelle wrote: SVN access should have been restored this weekend by sourceforge. I heard some project lost a couple of SVN revisions because the backup did not contain the latest state of affairs. Just as a word of warning. Michael

Re: [Jmol-developers] SVN access problem

2015-07-27 Thread Nicolas Vervelle
On Mon, Jul 27, 2015 at 1:11 PM, Michael Banck mba...@debian.org wrote: On Mon, Jul 27, 2015 at 01:02:17PM +0200, Nicolas Vervelle wrote: SVN access should have been restored this weekend by sourceforge. I heard some project lost a couple of SVN revisions because the backup did not contain

Re: [Jmol-developers] SVN access problem

2015-07-27 Thread Herman Bergwerf
Perhaps time to move to GitHub? (not sure about the limitations) On Mon, Jul 27, 2015, 13:24 Nicolas Vervelle nverve...@gmail.com wrote: On Mon, Jul 27, 2015 at 1:11 PM, Michael Banck mba...@debian.org wrote: On Mon, Jul 27, 2015 at 01:02:17PM +0200, Nicolas Vervelle wrote: SVN access

Re: [Jmol-developers] SVN access problem

2015-07-24 Thread Michael Banck
Hi, On Fri, Jul 24, 2015 at 11:26:06AM +0200, Rolf Huehne wrote: since a week (starting on July 17 2015) I have problems connecting to the SVN server for mirroring the scripting documentation with the following error message: - svn: E175002: Unable to connect to a