Am 20.02.2012 um 01:57 schrieb Jeff King: > On Sat, Feb 18, 2012 at 03:30:00AM -0800, Jakub Narebski wrote: > >> Igor <mrigor83@xxxxxxxxx> writes: >> >>> I'm running into an issue where I have to enter my pem certificate >>> password every time I git-svn fetch or git-svn dcommit. Vanilla svn >>> uses OS X KeyChain and remembers my password just fine. Is there a >>> known solution for this? Other users have ran into same issue as >>> described here: >>> >>> http://stackoverflow.com/questions/605519/does-git-svn-store-svn-passwords >> >>> However, that solution of removing .subversion folder did not work >>> for me. >> >> I don't know if it is svn that has to remember password, or git that >> has to remember password. Git 1.7.9 learned "credentials API" that >> allows integration with platform native keychain mechanisms, and I >> think OS X Keychain is one of examples / supported platforms (but it >> might not made it into core git)... though I am not sure if it affects >> git-svn, or only HTTP(S) transport. > > It does not affect git-svn currently. > > I have some thoughts on providing access to the credentials API for > scripts like git-svn (right now, it is accessible only by C git > programs). However, there is an important question: should password > prompting in git-svn behave like git, or behave like svn? > > So far, it has been the latter, and I think that is reasonable. The > resource that requires the credentials is an svn repo, not a git repo, > so you are more likely to want to share credentials for it with real > svn, and not other git commands. > IMHO a normal user would expect git-svn to store credentials in the same way as normal svn. I think this is the way it should be. Best regards, Nikolaus-- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html