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

Re: [RFC] Deal with HTTP 401 by requesting credentials.

From
Kevin Stange <kevin@steadfast.net>
Date
May 31, 2012, 23:18 UTC
Message-ID
<4FC7FC49.4030503@steadfast.net>
In-Reply-To
<4FC7EFB7.4090704@steadfast.net>
On 05/31/2012 05:24 PM, Kevin Stange wrote:
Show 5 quoted lines
> Apologies for anything wrong I might have done here.  I'm not used to
> procedures for this sort of patch submission, or terribly familiar with
> the code base.  I'm seeking advice on whether this approach is sane or
> completely crazy, and I'm willing to adjust it to make it suitable for
> inclusion.
Of course, I failed to get my email client to send the patch unwrapped.  Only one line appears to have been affected, but I don't think this is a final patch.  I'll be sure to make a proper submission for any future patches I send.  Sorry!
-- 
Kevin Stange
Chief Technology Officer
Steadfast Networks
http://steadfast.net
Phone: 312-602-2689 ext. 203 | Fax: 312-602-2688 | Cell: 312-320-5867
Previous: Kevin StangeNext: Jeff King
Message 2 of 8 in “[RFC] Deal with HTTP 401 by requesting credentials.”
  1. Kevin StangeMay 31, 2012
  2. Kevin StangeMay 31, 2012
  3. Jeff KingJun 1, 2012
  4. Junio C HamanoJun 1, 2012
  5. Jeff KingJun 5, 2012
  6. Kevin StangeJun 1, 2012
  7. Jeff KingJun 5, 2012
  8. Kevin StangeJun 5, 2012

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.