On Tue, Oct 04, 2011 at 02:12:02PM +0200, Michael J Gruber wrote: > > The latter is especially useful if you have put a username in your > > ~/.gitconfig, in which case you get: > > I'm actually wondering why git can't infer the user from > > https://user@xxxxxxxx > > with last week's next, at least. It can, and it has for some time. Part of the configurable-username thing was that it would be way nicer to just use a user-agnostic URL, because it means it's easier to share with other people. > > $ git push https://example.com/foo.git > > Password for 'user@xxxxxxxxxxx': > > > > which is a nice reminder. And it would happen to work with your askpass > > magic (I also wonder if it should mention the protocol and the repo, but > > most of the time that isn't relevant, and it does make the prompt harder > > to read). > > With the above, I can probably do without any magic: 'example.com' would > be the wallet key for the username (if I let the wallet store it) and > 'user@xxxxxxxxxxx' the key for the password, whether the username comes > from the wallet or from the config. (Again, why not from the URL?) Yeah, sorry, I should have said "ksshaskpass's magic". :) And yes, it can come from the URL. Mentioning the user in the password prompt is not as useful a reminder if it comes from: $ git push https://user@xxxxxxxxxxx/foo.git but, if it's something like: $ git clone https://user@xxxxxxxxxxx/foo.git [months pass] $ git push Password for 'user@xxxxxxxxxxx': then it's a nice reminder. -Peff -- 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