From: Kyle Neath <kneath@gmail.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git@vger.kernel.org
Subject: Re: The imporantance of including http credential caching in 1.7.7
Date: Wed, 7 Sep 2011 13:14:01 -0700 [thread overview]
Message-ID: <CAFcyEthuf49_kOmoLmoSSbNJN+iOBpicP4-eFAV5wL5_RffwGg@mail.gmail.com> (raw)
In-Reply-To: <4E6769E3.4070003@drmicha.warpmail.net>
Junio C Hamano <gitster@pobox.com> wrote:
> If this were a new, insignificant, and obscure feature in a piece of
> software with mere 20k users, it may be OK to release a new version with
> the feature in an uncooked shape.
For the sake of my paycheck, I should certainly hope not! I'm not at all
suggesting we merge what we have in. However, I do think this feature is
important enough to delay the release. I trust in the judgement of the core
members to know when something is ready for inclusion in master.
Michael J Gruber <git@drmicha.warpmail.net> wrote:
> So, it's been a year or more that you've been aware of the importance of
> this issue (from your/github's perspective), and we hear about it now,
> at the end of the rc phase.
I apologize if it sounds like that. I've been discussing this situation with
many people (including Jeff King) for a very long time now, and it was my
understanding that the credential caching was done and simply waiting for a
new release. This is the first I've heard that it will not be included in
1.7.7, so I'm voicing my opinion now. Admittedly, late in the game - and I
apologize for that.
I'd be happy to help in any capacity I can. Unfortunately I'm no C hacker, and
I've accepted that as a character flaw (it's something I'm working on). I'm
afraid I can't be of much help with the actual code. What I can provide is an
alternate viewpoint to the core team. A viewpoint of someone who's spent 3
years trying to make git easier for newcomers.
I urge the core team to think about what kind of opportunity we have here.
Credential caching isn't some minor feature. It's the last piece of the puzzle
that promotes Smart HTTP to a viable alternative over the git & ssh protocols.
Smart HTTP solves an huge collection of problems people have with using git
day to day. One URL to push privately and pull anonymously. No firewall
restrictions at universities or workplaces. Username & password
authentication. I get kind of turned on just thinking about it.
Kyle
next prev parent reply other threads:[~2011-09-07 20:14 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 [this message]
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
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=CAFcyEthuf49_kOmoLmoSSbNJN+iOBpicP4-eFAV5wL5_RffwGg@mail.gmail.com \
--to=kneath@gmail.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
/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).