actually, the @gmail.com shouldn't be required. Try your next checkin with
--username=jrgeerdes. The svn client doesn't cache your username on a
checkout because authentication isn't done at that time (it only caches
when challenged by the server). Most likely what is happening is that the
username on your machine is not jrgeerdes, and that's what's being passed
to the server for the challenge at commit time.
On 2:04 pm, Jeremy Geerdes <jrgeer...@gmail.com> wrote:
Well, that worked. Thanks for the help! I am curious, though. When I
ran the initial checkout, I ran it just as specified on the Source tab
(i.e., with --username jrgeerdes). To the best of my recollection, this
was how I have contributed to my other Code project, and it always
worked. Just curious why would I need to specify the @gmail.com now.
It's probably a silly noob question, though, so don't worry about
answering! Thanks!
Jeremy R. Geerdes
Effective website design & development
Des Moines, IA
For more information or a project quote:
http://jgeerdes.home.mchsi.com
jrgeer...@gmail.com
If you're in the Des Moines, IA, area, check out Debra Heights Wesleyan
Church!
--
You received this message because you are subscribed to the Google Groups "Project
Hosting on Google Code" group.
To post to this group, send email to google-code-host...@googlegroups.com.
To unsubscribe from this group, send email to
google-code-hosting+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-code-hosting?hl=en.
