Yes, I did have .netrc in place - which allows me to clone without password 
prompt.
it is only the push that gave me errors. here is the trace as requested. 
thanks for looking into this:

error: The requested URL returned error: 403 while accessing 
https://code.google.com/p/scigest/info/refs

fatal: HTTP request failed
panda:~/scigest[master]$ GIT_CURL_VERBOSE=1 git push
* About to connect() to code.google.com port 443 (#0)
*   Trying 74.125.67.100... * Connected to code.google.com (74.125.67.100) 
port 443 (#0)
* SSL connection using RC4-SHA
* Server certificate:
*  subject: C=US; ST=California; L=Mountain View; O=Google Inc; 
CN=*.google.com
*  start date: 2011-07-27 10:11:59 GMT
*  expire date: 2012-07-27 10:21:59 GMT
*  subjectAltName: code.google.com matched
*  issuer: C=US; O=Google Inc; CN=Google Internet Authority
*  SSL certificate verify ok.
> GET /p/scigest/info/refs?service=git-receive-pack HTTP/1.1
User-Agent: git/1.7.5.3
Host: code.google.com
Accept: */*
Pragma: no-cache

< HTTP/1.1 401 Unauthorized
< WWW-Authenticate: Basic realm="Google Code git Repository"
< Content-Type: text/html; charset=UTF-8
< X-Content-Type-Options: nosniff
< Date: Mon, 15 Aug 2011 22:17:27 GMT
< Server: git_frontend
< Content-Length: 11846
< X-XSS-Protection: 1; mode=block
< 
* Ignoring the response-body
* Connection #0 to host code.google.com left intact
* Issue another request to this URL: 
'https://code.google.com/p/scigest/info/refs?service=git-receive-pack'
* Re-using existing connection! (#0) with host code.google.com
* Connected to code.google.com (74.125.67.100) port 443 (#0)
* Server auth using Basic with user '[email address]'
> GET /p/scigest/info/refs?service=git-receive-pack HTTP/1.1
Authorization: Basic ZndhbmcyQGdtYWlsLmNvbTo=
User-Agent: git/1.7.5.3
Host: code.google.com
Accept: */*
Pragma: no-cache

* The requested URL returned error: 403
* Closing connection #0
* About to connect() to code.google.com port 443 (#0)
*   Trying 74.125.67.100... * Connected to code.google.com (74.125.67.100) 
port 443 (#0)
* SSL re-using session ID
* SSL connection using RC4-SHA
* Server certificate:
*  subject: C=US; ST=California; L=Mountain View; O=Google Inc; 
CN=*.google.com
*  start date: 2011-07-27 10:11:59 GMT
*  expire date: 2012-07-27 10:21:59 GMT
*  subjectAltName: code.google.com matched
*  issuer: C=US; O=Google Inc; CN=Google Internet Authority
*  SSL certificate verify ok.
* Server auth using Basic with user '[email address]'
> GET /p/scigest/info/refs HTTP/1.1
Authorization: Basic ZndhbmcyQGdtYWlsLmNvbTo=
User-Agent: git/1.7.5.3
Host: code.google.com
Accept: */*
Pragma: no-cache

* The requested URL returned error: 403
* Closing connection #0
error: The requested URL returned error: 403 while accessing 
https://code.google.com/p/scigest/info/refs

fatal: HTTP request failed

-- 
You received this message because you are subscribed to the Google Groups 
"Project Hosting on Google Code" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-code-hosting/-/naKXedbenz8J.
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-code-hosting?hl=en.

Reply via email to