Hi Frank,

Thanks for the reply. I am not using any password for the access. I have now 
installed the latest version of Tortoise SVN which i think is 1.4.6. Also, i 
have tried creating a new workspace and trying sync again but whatever i do i 
am still getting the same 503 error. Can you help ?

Hope your holidays were great !!

Thanks
Kulvinder Singh


----- Original Message ----
From: Frank Mantek <[EMAIL PROTECTED]>
To: [email protected]
Sent: Wednesday, January 2, 2008 1:39:36 PM
Subject: Re: SVN Update

sorry for the late reply, was on holiday break....


This is working fine for me. Are you using a password/account? Also verified 
that normal html access to the source is still working. What happens when you 
create a new workspace and try to sync again - maybe your client is getting 
corrupted somehow?


Frank Mantek
Google

On Dec 26, 2007, at 11:09 AM, Kulvinder Singh wrote:


Hi,
 
I keep local copy of Google Calendar .NET API on my machine to be synched up 
with the Google server at svn through Tortoise SVN. From last 15 -20 days 
whenever i try to do an update through SVN Update, i get a 503 error. The path 
i have set on my machine is :
 
http://google-gdata.googlecode.com/svn/trunk/clients/cs
 
for a folder named "cs" on my machine. I am not able to figure out what has 
went wrong where.
 
Can somebody help ?
 
Thanks
Kulvinder Singh




Looking for last minute shopping deals? Find them fast with Yahoo! Search.








      
____________________________________________________________________________________
Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Calendar Data API" group.
To post to this group, send email to 
[email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/google-calendar-help-dataapi?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to