From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Stefan Naewe <stefan.naewe@gmail.com>,
Sebastian Schuberth <sschuberth@gmail.com>,
Eric <eric.advincula@gmail.com>,
git@vger.kernel.org, msysgit@googlegroups.com
Subject: Re: [PATCH] Revert "http: don't always prompt for password"
Date: Tue, 13 Dec 2011 18:20:53 -0500 [thread overview]
Message-ID: <20111213232053.GE12432@sigill.intra.peff.net> (raw)
In-Reply-To: <20111213231909.GD12432@sigill.intra.peff.net>
On Tue, Dec 13, 2011 at 06:19:09PM -0500, Jeff King wrote:
> > Or just let the "dumb HTTP" die.
> >
> > I thought push over DAV has long been dead; is anybody using it for real?
>
> For the record, I have no problem whatsoever with letting it die. I just
> think we probably shouldn't do it accidentally during a release. ;)
BTW, one other solution, rather than reverting Stefan's patch, is to
just re-add the "unconditionally ask for a password" behavior back to
git-http-push, but not to the fetching side. Especially if we hope to
kill off git-http-push soon (after a deprecation period presumably),
then that lets it work in the meantime without hurting the other http
code. And it's really easy to do.
-Peff
next prev parent reply other threads:[~2011-12-13 23:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 20:17 [PATCH 1/2] t5540: test DAV push with authentication Jeff King
2011-12-13 20:25 ` [PATCH] Revert "http: don't always prompt for password" Jeff King
2011-12-13 21:09 ` Junio C Hamano
2011-12-13 21:22 ` Eric Advincula
2011-12-13 23:18 ` Jeff King
2011-12-13 23:19 ` Jeff King
2011-12-13 23:20 ` Jeff King [this message]
2011-12-14 0:11 ` Jeff King
2011-12-14 0:33 ` Junio C Hamano
2011-12-14 8:20 ` Matthieu Moy
2011-12-13 21:25 ` Junio C Hamano
2011-12-13 23:10 ` Jeff King
2011-12-13 21:28 ` [PATCH 1/2] t5540: test DAV push with authentication Sebastian Schuberth
2011-12-13 23:16 ` 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=20111213232053.GE12432@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=eric.advincula@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=msysgit@googlegroups.com \
--cc=sschuberth@gmail.com \
--cc=stefan.naewe@gmail.com \
/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).