Guten Tag arun prasath,
am Freitag, 18. Dezember 2015 um 08:33 schrieben Sie:
> I am running svnserve for client access through TortoiseSVN. This
> is for users who wants to checkout and checkin the code.
TortoiseSVN can handle checkouts and such over HTTP as well, there's
no need to use svnserve
Hi Ryan,
Thanks for the info.
I am running svnserve for client access through TortoiseSVN. This is for
users who wants to checkout and checkin the code.
There are some users who just want to browse the code in Internet Explorer.
The http in browser is required for users who browse code without ch
Has there been any thought to added SSL/TLS to the svn protocol? Setting up
Apache for https is a bit heavy and SSH requires the existence of local users.
Adding TLS doesn't seem like it would be that hard and would help when using
SASL/LDAP when passing plaintext passwords.
On Dec 17, 2015, at 8:09 AM, arun prasath wrote:
> I have situation which needs your suggestion and help in setting up the
> svn1.9.2 with svnserve + http access in browser. My below talks about my svn
> setup.
> SVN working method:
> After installation, the svn://servername/reponame is working
Hi Team,
I have situation which needs your suggestion and help in setting up the
svn1.9.2 with svnserve + http access in browser. My below talks about my
svn setup.
*SVN working method:*
After installation, the svn://servername/reponame is working. But
http://servername/reponame is not working and
Hi
I just wanted to report that we are affected by this bug and would be grateful
if the developers will include Marc Strapetz's patch (submitted on developers
mailing list on 11 Dec) in the next Subversion release.
Best regards
David
