From: Junio C Hamano <gitster@pobox.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Grégoire Barbier" <devel@gbarbier.org>,
git@vger.kernel.org
Subject: Re: [PATCH] http-push: making HTTP push more robust and more user-friendly
Date: Mon, 21 Jan 2008 14:05:01 -0800 [thread overview]
Message-ID: <7v1w8aygvm.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.LNX.1.00.0801211539320.13593@iabervon.org> (Daniel Barkalow's message of "Mon, 21 Jan 2008 16:30:40 -0500 (EST)")
Daniel Barkalow <barkalow@iabervon.org> writes:
> On Mon, 21 Jan 2008, Junio C Hamano wrote:
>
>> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>>
>> > IMHO it is safer to disable it for curl < 7.0xa -- even if it affects a
>> > number of distros -- than to give the illusion that it works, when it does
>> > not.
>> >
>> > As for fixing it in the non-MULTI case, I have a hunch that Mike's
>> > cleanups will help that, but that this is a 1.5.5 feature.
>> >
>> > So, I would like to read in the ReleaseNotes something like this:
>> >
>> > -- snip --
>> > Support for pushing via HTTP was broken with curl versions prior to 7.16,
>> > so we disabled it for now. However, it is likely that a major cleanup of
>> > the http transport code -- scheduled after the release of git 1.5.4 --
>> > will be supported with more curl versions.
>> > -- snap --
>>
>> That's tempting but I suspect that it might be a wrong approach.
>>
>> I think two important questions are:
>>
>> * Do we know that the current code is broken for everybody, or
>> just broken for the majority of people who do nontrivial
>> things?
>>
>> * Is the code in 1.5.3.8 any better? IOW, did we make it worse
>> during 1.5.4 cycle?
>
> I believe that the move to transport.c didn't change anything except
> cleaning up linking conflicts and moving the dispatch by URL method code.
> I suppose something could have gotten messed up in dealing with the
> linking conflicts, but I don't think it actually did.
Ok, so copying 1.5.3.8 http-push to include in 1.5.4 would not
make it work, it sounds like. Then I guess Dscho's notice (and
the same notice with disabling http-push without MULTI in
1.5.3.9) would be the sane thing we should do in the short term.
next prev parent reply other threads:[~2008-01-21 22:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-13 19:02 [PATCH] http-push: making HTTP push more robust and more user-friendly Grégoire Barbier
2008-01-13 19:02 ` [PATCH] http-push: fix webdav lock leak Grégoire Barbier
2008-01-13 19:02 ` [PATCH] http-push: disable http-push without USE_CURL_MULTI Grégoire Barbier
2008-01-13 23:01 ` [PATCH] http-push: making HTTP push more robust and more user-friendly Junio C Hamano
2008-01-14 11:21 ` Johannes Schindelin
2008-01-14 19:35 ` Junio C Hamano
2008-01-14 20:22 ` Johannes Schindelin
2008-01-19 15:21 ` Grégoire Barbier
2008-01-19 23:18 ` Johannes Schindelin
2008-01-21 10:09 ` Grégoire Barbier
2008-01-21 10:20 ` Junio C Hamano
2008-01-21 10:27 ` Grégoire Barbier
2008-01-21 11:06 ` Junio C Hamano
2008-01-21 12:17 ` Johannes Schindelin
2008-01-21 20:18 ` Junio C Hamano
2008-01-21 20:29 ` Mike Hommey
2008-01-22 0:58 ` Johannes Schindelin
2008-01-22 1:34 ` Junio C Hamano
2008-01-22 1:38 ` Johannes Schindelin
2008-01-22 2:04 ` Junio C Hamano
2008-01-22 2:14 ` Johannes Schindelin
2008-01-21 21:30 ` Daniel Barkalow
2008-01-21 22:05 ` Junio C Hamano [this message]
2008-01-21 23:12 ` Grégoire Barbier
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=7v1w8aygvm.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=barkalow@iabervon.org \
--cc=devel@gbarbier.org \
--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.
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).