From: Jeff King <peff@peff.net>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: Kyle Neath <kneath@gmail.com>, git@vger.kernel.org
Subject: Re: The imporantance of including http credential caching in 1.7.7
Date: Fri, 9 Sep 2011 14:34:24 -0400 [thread overview]
Message-ID: <20110909183424.GD28480@sigill.intra.peff.net> (raw)
In-Reply-To: <4E69C8F0.9070204@drmicha.warpmail.net>
On Fri, Sep 09, 2011 at 10:06:08AM +0200, Michael J Gruber wrote:
> > So I think the wheels have been turning on this for quite a while from
> > GitHub's perspective.
>
> Thanks for clarifying. While it should make no difference for the
> acceptance of patches, it's great to see GitHub invest into scratching
> their Git itches, and thus contribute back. That's how open source works
> as a business model :)
Yes. I don't often enough mention how awesome GitHub is for funding me
and giving me a free hand to improve git. They're doing everything
right. So let me mention it here one more time. :)
> > In the meantime, the best thing we can do to push it forward is to write
> > helpers. I implemented some basic ones that should work anywhere, but
> > aren't as nice as integration with existing keychains. Some people are
> > working on Linux ones. The single best thing GitHub can do to push this
> > forward right now is to provide a well-written OS X Keychain helper, and
> > to provide feedback on whether git's end of the API is good enough.
>
> ... and one for Git on Windows? It seems we're lacking both Win and OS X
> developers here.
I mentioned OS X because of Kyle's mention of the GitHub for Mac client.
But yes, I do think in the long term we want something similar on
Windows. GitHub recently hired a developer with some Windows experience;
I'll try to see if he's interested in writing a credential helper.
-Peff
prev parent reply other threads:[~2011-09-09 18:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-07 5:33 The imporantance of including http credential caching in 1.7.7 Kyle Neath
2011-09-07 7:46 ` Sverre Rabbelier
2011-09-07 8:11 ` Kyle Neath
2011-09-07 11:21 ` Junio C Hamano
2011-09-07 12:56 ` Michael J Gruber
2011-09-07 20:14 ` Kyle Neath
2011-09-07 21:08 ` Junio C Hamano
2011-09-07 23:01 ` Philip Oakley
2011-09-07 23:38 ` Junio C Hamano
2011-09-08 13:17 ` Michael J Gruber
2011-09-08 15:02 ` John Szakmeister
2011-09-08 19:18 ` Jeff King
2011-09-09 8:05 ` Michael J Gruber
2011-09-09 8:12 ` Miles Bader
2011-09-09 18:27 ` Jeff King
2011-09-08 19:10 ` Jeff King
2011-09-09 8:06 ` Michael J Gruber
2011-09-09 10:15 ` Ted Zlatanov
2011-09-09 10:32 ` John Szakmeister
2011-09-09 10:48 ` Erik Faye-Lund
2011-09-09 10:54 ` John Szakmeister
2011-09-09 13:33 ` Ted Zlatanov
2011-09-09 13:31 ` Ted Zlatanov
2011-09-09 18:34 ` Jeff King [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110909183424.GD28480@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=kneath@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).