From: Junio C Hamano <gitster@pobox.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>,
git@vger.kernel.org, "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>,
"Jeff King" <peff@peff.net>, "Shawn Pearce" <spearce@spearce.org>
Subject: Re: [PATCH v2 2/2] Update documentation for http.continue option
Date: Wed, 23 Oct 2013 08:47:57 -0700 [thread overview]
Message-ID: <xmqq61sornte.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20131022233257.GA9464@google.com> (Jonathan Nieder's message of "Tue, 22 Oct 2013 16:32:58 -0700")
Jonathan Nieder <jrnieder@gmail.com> writes:
> Wouldn't a natural fix be to *always* use "Expect: 100-continue" when
> and only when the probe_rpc() revealed a server supporting
> GSS-Negotiate authentication?
A stupid question. Is GSS-Negotiate the only special case?
next prev parent reply other threads:[~2013-10-23 15:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 22:35 [PATCH v2 0/2] HTTP GSS-Negotiate improvements brian m. carlson
2013-10-11 22:35 ` [PATCH v2 1/2] http: add option to enable 100 Continue responses brian m. carlson
2013-10-11 23:43 ` Jonathan Nieder
2013-10-12 0:03 ` brian m. carlson
2013-10-11 22:35 ` [PATCH v2 2/2] Update documentation for http.continue option brian m. carlson
2013-10-11 23:50 ` Jonathan Nieder
2013-10-12 0:26 ` brian m. carlson
2013-10-18 22:15 ` brian m. carlson
2013-10-22 23:00 ` Junio C Hamano
2013-10-22 23:32 ` Jonathan Nieder
2013-10-23 1:34 ` Jonathan Nieder
2013-10-23 3:00 ` brian m. carlson
2013-10-23 3:21 ` Shawn Pearce
2013-10-23 22:56 ` brian m. carlson
2013-10-25 7:17 ` Jeff King
2013-10-25 20:56 ` brian m. carlson
2013-10-23 15:47 ` Junio C Hamano [this message]
2013-10-23 22:53 ` brian m. carlson
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq61sornte.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
--cc=spearce@spearce.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).