git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: The imporantance of including http credential caching in 1.7.7

From
Kyle Neath <kneath@gmail.com>
Date
Sep 7, 2011, 20:14 UTC
Message-ID
<CAFcyEthuf49_kOmoLmoSSbNJN+iOBpicP4-eFAV5wL5_RffwGg@mail.gmail.com>
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
Previous: Michael J GruberNext: Junio C Hamano
Message 6 of 24 in “The imporantance of including http credential caching in 1.7.7”
  1. Kyle NeathSep 7, 2011
  2. Sverre RabbelierSep 7, 2011
  3. Kyle NeathSep 7, 2011
  4. Junio C HamanoSep 7, 2011
  5. Michael J GruberSep 7, 2011
  6. Kyle NeathSep 7, 2011
  7. Junio C HamanoSep 7, 2011
  8. Philip OakleySep 7, 2011
  9. Junio C HamanoSep 7, 2011
  10. Michael J GruberSep 8, 2011
  11. John SzakmeisterSep 8, 2011
  12. Jeff KingSep 8, 2011
  13. Michael J GruberSep 9, 2011
  14. Miles BaderSep 9, 2011
  15. Jeff KingSep 9, 2011
  16. Jeff KingSep 8, 2011
  17. Michael J GruberSep 9, 2011
  18. Ted ZlatanovSep 9, 2011
  19. John SzakmeisterSep 9, 2011
  20. Erik Faye-LundSep 9, 2011
  21. John SzakmeisterSep 9, 2011
  22. Ted ZlatanovSep 9, 2011
  23. Ted ZlatanovSep 9, 2011
  24. Jeff KingSep 9, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.