Re: [ANNOUNCE] Git 1.7.8.rc0
- From
Michael J Gruber <git@drmicha.warpmail.net>
- Date
- Nov 2, 2011, 10:27 UTC
- Message-ID
- <4EB11B13.1060003@drmicha.warpmail.net>
- In-Reply-To
- <loom.20111101T211624-511@post.gmane.org>
[Re-adding cc's]
Stefan Naewe venit, vidit, dixit 01.11.2011 21:18:
Show 24 quoted lines
> Stefan Naewe <stefan.naewe <at> gmail.com> writes: > >> Push with https works, if the URL looks e.g. like this: >> >> https://github.com/user/repo.git >> >> rather than this >> >> https://user <at> github.com/user/repo.git >> >> and having a ~/.netrc like this >> >> machine github.com login user password YouDontWantToKnow >> >> If the URL contains 'user@' I get the 'need ENTER' behaviour. >> > > Another update: > > If I revert deba493 the 'need ENTER' is gone and everything works as above. > > > Stefan >
I can confirm that (and feel partly responsible given the history of of deba493). For the record: A simple test looks like
SSH_ASKPASS='' git push -n bitbucket Password for 'bitbucket.org':
which succeeds with a simple ENTER when you have the (log and) PW in .netrc for that host, and your config says https://user@host.
The workaround is to remove 'user@' from the url in gitconfig, it is not needed nor used, probably: I haven't checked yet, but that would mean we can't have two different logins on the same server in .netrc. Can we?
I'll try to have a look later, too.
Michael