From: Kevin Stange <kevin@steadfast.net>
To: git@vger.kernel.org
Subject: Re: [RFC] Deal with HTTP 401 by requesting credentials.
Date: Thu, 31 May 2012 18:18:33 -0500 [thread overview]
Message-ID: <4FC7FC49.4030503@steadfast.net> (raw)
In-Reply-To: <4FC7EFB7.4090704@steadfast.net>
On 05/31/2012 05:24 PM, Kevin Stange wrote:
> 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
next prev parent reply other threads:[~2012-05-31 23:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 22:24 [RFC] Deal with HTTP 401 by requesting credentials Kevin Stange
2012-05-31 23:18 ` Kevin Stange [this message]
2012-06-01 8:35 ` Jeff King
2012-06-01 17:01 ` Junio C Hamano
2012-06-05 16:23 ` Jeff King
2012-06-01 17:02 ` Kevin Stange
2012-06-05 16:28 ` Jeff King
2012-06-05 16:41 ` Kevin Stange
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=4FC7FC49.4030503@steadfast.net \
--to=kevin@steadfast.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).