Announcement

Collapse
No announcement yet.

Svn takes too muching time in switching brunches, cleanup

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    ok but some branches is not shown after updating from svn

    Comment


    • #17
      Do you know the version of SVN on the server?
      What version did you update to on the client?

      Comment


      • #18
        i have svn 1.6 version on server and client tortoise is 1.7.7

        Comment


        • #19
          Sorry about asking for the versions again: I was on a very small display and didn't scroll back to the top. If there was an error I really need to see that error. To repeat, the "200 OK" is not an error - that's saying everything is fine. So if something failed there should be an error - something other than a 200-series HTTP status. If your server is doing proper logging then the error should be recorded there (at least). If it's Apache then in the "error_log" (or "ssl_error_log"). If some other server then, well, look around. All log file entries should be time-stamped and your user should be able to tell you the time when the failure happened (or you need to let them know that they need to write that down when it next happens). Cheers.

          Comment

          Working...
          X