30 Nov
2011
30 Nov
'11
09:09
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-11-30 01:17, Gabriel [SGT] wrote:
On Tue, Nov 29, 2011 at 9:09 PM, Carlos E. R. <> wrote:
Because if I am (I do not know), then it is an issue for me.
It depends, are you using https:// or svn+ssh:// ? I bet it's https :) Anyway, the subversion client can manage both. The access will be the same as it was when we started (https), using the opensuse svn.
I see, it depends on how we originally called it. Let me see... I have a ~/.subversion dir... I see the "https://forgesvn1.novell.com:443" string, that's old. Ok, I see https://svn.berlios.de:443, then I have no problem.
- -- Cheers / Saludos,
Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
iEYEARECAAYFAk7V8sgACgkQtTMYHG2NR9X3XgCgjFVvXnCC0Wgyads4Jav0S+9G
4iwAn2BYFnEAlDpVb0aBgNa0z6pkuBoc
=99vf
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org
To contact the owner, e-mail: opensuse-translation+owner@opensuse.org