Jeff King <peff@xxxxxxxx> writes: > It means that you can get convenient credential handling (whether it's > because you've configured a username, or you're getting it from a > wallet, or caching, or whatever) with: > > git push https://github.com/peff/git.git && > git push https://github.com/peff/foo.git > > which should hopefully just prompt you once (and a configured username > would have to be configured only once for the host). > > And it comes at the cost that there's not a good way to use two > different identities for the same host. Yes, both "just prompt you once" and "would have to be configured only once" cut both ways, and that is mildly disturbing to my taste. If we annotate the remote in .git/config perhaps like this: [remote "foo"] url = https://github.com/peff/foo.git auth_context = "foo project at github" ... [remote "bar"] url = https://github.com/peff/bar.git auth_context = "bar project at github" and have "git push foo" pass the auth_context to the credential backend, which can notice the two projects are in different context and cache two identities under different contexts, would it be a good workaround for the issue? Then, a remote that does not have auth_context configured would use "https:github.com" that is machine-generated (in http.c in your code), but that can easily be overridden if/as necessary. > I tried to optimize for the common case (many repos under one identity) > than the uncommon (many identities under one host). As I am not convinced if this statement is true. -- 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