Re: The imporantance of including http credential caching in 1.7.7
- From
Kyle Neath <kneath@gmail.com>
- Date
- Sep 7, 2011, 08:11 UTC
- Message-ID
- <CAFcyEtihOVz17-3QRZLSNE-4yS2vBHaaUzHng+ciwK0usSm1dA@mail.gmail.com>
- In-Reply-To
- <CAGdFq_h3KNuGuhhY2Zv-dHWqAY4Wq3HHBGh2f53rWzDT9PzSgQ@mail.gmail.com>
On Wed, Sep 7, 2011 at 12:46 AM, Sverre Rabbelier <srabbelier@gmail.com> wrote:
> Junio mentioned in WC that he wants to see some feedback on it's > usage, perhaps that you can help provide this by providing a git > patched with this functionality to some of your users and see how they > respond?
Perhaps this is where things get complicated. Due to the nature of the people I'm discussing (people afraid of SSH keys), getting them to run a custom version of git is pretty far out of the question. Peff alluded to this in his reply.
I think the best evidence I can provide is in context of GitHub for Mac. GitHub for Mac defaults to Smart HTTP, with the credentials cached in OSX's Keychain. Effectively, it functions as a patched git with credential caching.
Two months after shipping, we have around 20,000 people that use the application regularly. In that time, we've gotten a ton of positive feedback. So there is a great number of people interested in a git client that uses Smart HTTP. One of the bigger complaints we get is that people constantly have to enter their username & password if they choose to drop to the command line.
Of course, this is all fuzzy data since it's not really comparable with git core. But it's the only data I have.
Then again, perhaps the fact that we spent development time hacking around git's limitation is a data point in itself. Git GUI developers are spending development time to fill a hole in git core.
Kyle